System and method for dynamic uploading and execution of applications and drivers between devices

ABSTRACT

A methodology for dynamic (i.e., run-time) uploading and execution of applications and drivers between devices (e.g., between “client” device and one or more (host) devices), in a fully automated manner, is described. The device which is to be hosted (e.g., the “client” device) initially probes its environment to determine which device or devices it is attached to (e.g., the “host” device(s)). Once it has correctly discerned the relevant host or target device(s), the client device includes the capability of immediately sending out (i.e., uploading) a particular driver or application (i.e., object or file of interest) for placement, and ultimately execution, at the host device. Once the particular object or file of interest has been “injected” into the host device and is executing, the client device may simply revert to a “listening mode” in which it waits to be told what to do (i.e., receive commands from the application or driver which is now executing at the host device). This approach is particularly well-suited for devices which serve as “add-on” devices (clients) to other devices (hosts) that are “smarter,” for instance, including more processing capability and/or memory. In this scenario, the client device enters into a dialog with a device with more resources for the purpose of harnessing the resources of the host device for operating the client or add-on device. The client device is, using this approach, able to start running (i.e., driver-directed operation) immediately upon attachment to a host device that can be identified.

RELATED APPLICATIONS

The present application is related to and claims the benefit of priority of the following commonly-owned non-provisional application(s): application Ser. No. 09/660,531, filed Sep. 13, 2000, entitled “System and Method for Dynamic Uploading and Execution of Applications and Drivers between Devices”, of which the present application is a Continuation-in-part application thereof. The present application is also related to the following commonly-owned application(s): application Ser. No. 09/537,001, filed Mar. 28, 2000, entitled “Improved Digital Camera Device and Methodology for Wireless Progressive Transmission of Digital Images”. The disclosures of each of the foregoing applications are hereby incorporated by reference in their entirety, including any appendices or attachments thereof, for all purposes.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

BACKGROUND OF THE INVENTION

The present invention relates generally to system and methodology for dynamic or run-time uploading of an application or driver of interest from a first device to a second device, upon connecting the two devices together, and thereafter executing the application or driver at the second device.

Today, a multitude of different types of devices may be intermittently connected together for a particular user purpose. For example, many of the digital camera devices available today include the capability of connecting to different types of modules. Examples include modules that can transmit the camera's image data, modules that can print the image data, and modules that can display the image data, just to name a few. In order to support meaningful dialog between such devices, it is necessary to provide a mechanism that allows the camera device to identify what target or host device it is connected to and vice versa (i.e., identifying the camera device to the target device), as well as a mechanism that allows a program (e.g., driver) to run on the target device so that the target device may correctly communicate with the camera device. For example, a driver program or application executing at the target device can issue appropriate commands to the camera device for determining what image data (photos) exist on the camera device, so that they may be offloaded onto the target device for viewing, printing, or storing.

Generically speaking, a “driver” is a software program that controls a device, typically allowing that device to interoperate with other devices. For example, a printer driver allows a corresponding printing device to interoperate with software programs operating on a desktop computer that the printer is connected to. A driver acts like a translator between the device and programs that use the device. Devices typically include their own set of specialized commands that only its driver knows. At the same time, most programs prefer to access devices by using generic commands. The driver, therefore, may serve as a go-between by accepting generic commands from a program and then translates them into specialized commands for the device. Many drivers, such as keyboard drivers, come with a user's operating system. For other devices, the system is required to load a new driver when the user connects the device to his or her computer.

In the early days of personal computing, a user was required to manually install the appropriate driver for any new device that the user connected to his or her computer. More recently, that manual approach has been abandoned in favor of a “plug and play” approach. As an example familiar to PC users, today “plug and play” PCI bus cards (e.g., video graphics cards and sound cards) include code within them that triggers loading at operating system startup of a particular driver. “PCI” is an acronym for Peripheral Component Interconnect, a local bus standard developed by Intel Corporation. If the operating system (e.g., Windows 98) is able to locate a copy of the driver for a newly-installed PCI bus card, the driver is automatically loaded by the operating system to support operation of that PCI bus card. Note in particular with this approach, however, the host device (e.g., PC) must either already possess a copy of the relevant driver (e.g., in the Windows “cabinet” files) or the user is required to manually furnish the driver (e.g., by inserting a floppy disk or CD including the relevant driver).

In practice, the approach has been less than “plug and play.” Often, the operating system is unable to recognize a newly-installed device or, worse, “crashes” (i.e., hangs) while attempting to uncover nearly-installed devices. Another problem is that, even if a newly-installed device is recognized, the operating system is unable to automatically locate a copy of an appropriate driver for that device. In that situation, the system resorts to prompting the user to indicate where a copy may exist, and in some cases requires the user to manually install and configure the appropriate driver. Given these and other problems that have beset “plug and play,” the approach has been given the more dubious title of “plug and pray” by the computer industry press. Nevertheless, “plug and play” architecture represents perhaps the first serious attempt to provide some degree of automated driver installation.

With the ever-increasing popularity of Internet-based computing, it is not surprising that others have turned to the Internet in an effort to provide dynamic loading of drivers and other applications. For instance, as the result of using a Web browser, a user may trigger the automatic downloading of a particular driver. In this example, the driver is transferred from a Web server to the user's PC using HTTP protocol. HTTP or “HyperText Transfer Protocol” is the underlying protocol used by the World Wide Web. HTTP defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. Using HTTP in the Internet environment, “plug-in” functionality can be provided that supports some degree of automated driver or application installation and startup loading. A plug-in is a software (or hardware) module that adds a specific feature or service to a larger system. For example, there are number of plug-ins for the Netscape Navigator browser that enable it to display different types of audio or video messages.

Despite the multitude of approaches available for automating driver installation and startup loading, current approaches have significant shortcomings when attempting to connect two devices together. Many different types of devices exist and, expectedly, have disparate characteristics as to how they initially respond to a communication (between devices). In particular, many devices today “speak differently” (i.e., employ different communication protocols), thus preventing several of these devices from communicating with one another for purposes of device identification and driver-loading. For instance, the above plug-in approach basically assumes that all devices speak the same language, such as using HTTP commands over TCP/IP (Transmission Control Protocol/Internet Protocol, the suite of communications protocols used to connect hosts on the Internet). However, even the underlying communication infrastructure—TCP/IP—may not even be running initially on a particular target or host device of interest. Thus, one may not even rely on TCP/IP being available, at least initially, on a particular target device. (For an introduction to TCP/IP, see e.g., RFC 1180: A TCP/IP Tutorial, the disclosure of which is hereby incorporated by reference. A copy of RFC 1180 is currently available at ftp://ftp.isi.edu/in-notes/rfc1180. txt).

To date, these shortcomings have yet to be adequately addressed. As a result, realization of a completely transparent “plug and play” architecture has remained elusive. What is needed is an approach where a first device (e.g., digital camera device) may automatically upload and install an application or driver of interest to a second device (e.g., handheld computing device, that may “host” the digital camera device), upon the two devices being connected together. The present invention fulfills this and other needs.

SUMMARY OF THE INVENTION

A methodology for dynamic (i.e., run-time) uploading and execution of applications and drivers between devices (e.g., between “client” device and one or more (host) devices) in an automated manner is described. The device which is to be hosted (e.g., the “client” device) initially probes its environment to determine which device or devices it is attached to (e.g., the “host” device(s)). Once it has correctly discerned the relevant host or target device(s), the client device includes the capability of immediately sending out (i.e., uploading) a particular driver or application (i.e., object or file of interest) for placement, and ultimately execution, at the host device. Once the particular object or file of interest has been “injected” into the host device and is executing, the client device may simply revert to a “listening mode” in which it waits to be told what to do (i.e., receive commands from the application or driver which is now executing at the host device). In the currently-preferred embodiment, a digital camera device serves as a “client” device, which may connect to a variety of “host” devices (e.g., cellular phone, PDA (Personal Digital Assistant) handheld device, or the like).

The overall method or process of the present invention may be summarized as follows. The process gets underway upon the establishment of a connection (wireless or wireline) between a client device and a host device; the connection may be permanent or temporary. Starting with default registry information stored in a configuration registry, the client device probes for any host devices. This task falls specifically on a PHY (physical) manager. Based on the information uncovered by this probing, the registry is updated, with information describing discovered host devices and corresponding communication information relevant to each such discovered host device. As part of this step, the PHY manager will ensure TCP/IP connectivity to each such host device.

Now, the method may proceed with injection of the application or driver (or other executable object of interest) into the host device(s). The method may examine the registry for determining each host device that is connected, as this will determine what specific task(s) must be undertaken for performing injection (i.e., to inject an appropriate application or driver into each such host device). A TCP/IP session is established with the host device, for the specific purpose of injecting the file or object of interest (e.g., application or driver). The file is opened on the client device; as part of this process, a client-side file handle is obtained. From the perspective of the client device, the file is simply a binary object to be injected. The specific relevance of the file will be uncovered at the host device, when the file is ultimately executed at the host device. Having obtained a valid file handle for the file to be injected, the method may now proceed to package the file contents for transmission to the host device. In the currently-preferred embodiment, the XML protocol is employed for this packaging. Now, using TCP/IP, the packaged file may be transmitted (streamed) from the client device to the host device. In conjunction with this step, a host-side file handle is returned to the client device.

At this point, the method is now ready to trigger execution of the just-injected application or driver at the host device. Using the host-side file handle, the method instructs the host to now execute the just-injected application or driver. Host-side execution may require host-specific operations. In the straightforward case, the host is simply instructed to begin execution of the application or driver. If the host device does not support that functionality, however, execution of the application or driver may be accomplished through indirect means, such as instructing the host to “restart” itself and thereupon execute the application or driver (e.g., by placing the application or driver in a location where the host will automatically load it for execution upon startup). Thereafter, operation between the client and host devices continues as specified in the now-executing application or driver, which itself in turn may unpackage other drivers for execution. In a typical operation, the application or driver would issue particular commands to the client device, for instance, requesting that the client device transmit particular information that is to be processed by the host device, such as uploading digital photographs from the client device to the host device, for wireless transmission by the host device to yet another device (e.g., server computer).

This approach is particularly well-suited for devices which serve as “add-on” devices (clients) to other devices (hosts) that are “smarter,” for instance, including more processing capability and/or memory. In this scenario, the client device enters into a dialog with a device with more resources for the purposes of harnessing the resources of the host device for operating the client or add-on device. The client device is, using this approach, able to start running (i.e., driver-directed operation) immediately upon attachment to a host device that can be identified.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram illustrating a device, in the preferred embodiment a digital camera device, that is suitable for implementing the present invention.

FIG. 1B is a block diagram illustrating a digital computer that may interoperate with the digital camera device of FIG. 1A.

FIG. 2 is a block diagram of a software system suitable for controlling the computer of FIG. 1B.

FIG. 3 is a block diagram of an application/driver uploader system of the present invention, which is embodied in the digital camera device of FIG. 1A.

FIGS. 4A-B are flowcharts illustrating the overall methodology of operation for the application/driver uploader system of FIG. 3.

DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT

The following description will focus on the presently-preferred embodiment of the present invention, which operates in an environment typically including a variety of computing or information-storing devices (e.g., desktop computers, server computers, and portable computing devices), that are occasionally or permanently connected to one another where device-specific driver support is desired. In particular, the following description focuses on an embodiment of the present invention in a digital camera device, the currently-preferred embodiment, which may be occasionally connected to a multitude of different “host” devices, such as a Palm™ handheld computer or a cellular phone. However, those skilled in the art will appreciate that the present invention may be embodied in practically any device that is intended to be connected to another device (or devices). Further, the description focuses on implementation of portions of the invention in a connected environment including computers, such as an IBM-compatible computer running under Microsoft® Windows 2000, with Internet support. The present invention, however, is not limited to any particular one application or any particular environment. Instead, those skilled in the art will find that the system and methods of the present invention may be advantageously embodied on a variety of different platforms, including Macintosh, Linux, BeOS, Solaris, UNIX, NextStep, and the like, as well as special-purpose operating systems (e.g., digital camera operating systems). Therefore, the description of the exemplary embodiments which follows is for purposes of illustration and not limitation.

Basic System

A. Digital Camera Hardware

FIG. 1A is a block diagram illustrating a basic image capturing and recording system 100 suitable for implementing the present invention. For purposes of illustration, the following focuses on implementation of the system 100 as a digital camera. However, as noted above, for purposes of implementing the methodology of the present invention, the system 100 may also be implemented in a variety of other devices that are intended to be connected (including, occasionally connected) to yet other devices.

As shown in FIG. 1A, the system 100 includes a Sensor 101, a Shutter Actuator 103, an Image Processor 102, an Image (DRAM) Memory 104, a (Central) Processor 106, a Keypad and Controls 108, a Program Code Flash Memory 107, a (System) Memory 105, a Direct View Display or Viewfinder 109, a Hot Shoe Interface 110, and a “Digital Film” Flash Memory 111. As illustrated, these various components communicate with one another using a bus architecture including, for instance, an Address Bus, a Data Bus, and an I/O (Input/Output) Bus.

The system 100 employs the Sensor 101 for basic image capture. The Sensor 101 operates, in essence, by capturing light and transforming that into electrical voltage levels. A suitable sensor is available from a variety of vendors, including VLSI Vision, Motorola, and Toshiba. In a preferred embodiment, the Sensor 101 includes, for example, a 1280×1024 color CMOS sensor, such as a VLSI Vision VVL 6801 CMOS sensor. However, other sensor technology is suitable, including CCD sensors.

The Sensor 101 must, of course, be part of a larger assembly to operate. Specifically, the Sensor 101 operates in conjunction with a lens assembly (not shown), or other optics to focus an image onto the sensor. The optics themselves are controllable, for instance, using a conventional aperture, focus, and shutter control mechanisms. The currently-preferred embodiment uses an 18 mm fixed-focal length, fixed-aperture lens assembly to provide a broad depth of field. The lens assembly employs two manual slide controls, a macro lens control, and an exposure control. The macro control switches from normal to close-up mode by sliding a macro lens in and out of the lens assembly to provide normal or extreme close-up capability. The exposure control switches from normal to bright light by sliding a neutral gray filter in and out of the lens assembly. Aside from choosing normal or bright light, and normal or close-up mode, the camera requires no manual focusing, shutter speed or aperture adjustment. Operation is as simple as point and shoot. The Sensor 101, on the other hand, operates under control of the Image Processor 102, which will now be described.

The Image Processor 102, which basically operates as a state machine, provides overall control for the Sensor 101. In operation, the Image Processor 102 controls the Sensor 101 by, in effect, telling it what to do and when. For instance, the Image Processor 102 issues timing signals to the Sensor 101 for indicating how the Sensor 101 should record and stream out image data. Further, the Image Processor 102 provides general Input/Output (I/O) control that allows one to coordinate control of the sensor with other electromechanical peripherals, such as a shutter, lens aperture, or the like.

Actual implementation of the Image Processor 102 itself may be accomplished in a variety of different ways. For a microprocessor-based implementation, for instance, the Image Processor 102 may be implemented as a microprocessor (e.g., PowerPC 823 microprocessor, available from Motorola, Inc. of Schaumburg, Ill.) with DSP (digital signal processing) logic blocks, memory control logic blocks, video control logic blocks, and interface logic. Alternatively, the Image Processor 102 may be implemented as a “camera on a chip(set)” using, for instance, a Sierra Imaging Raptor I or II chipset (available from Sierra Imaging, Inc. of Scotts Valley, Calif.), a Sound Vision Clarity 1 or 2 chipset (available from Sound Vision, Inc. of Framingham, Mass.) or similar chipset that integrates a processing core with image processing periphery. in a preferred embodiment, the Image Processor 102 preferably supports hardware implementation of a wavelet-transform engine complete with a wavelet-transform filter bank, so that the wavelet-transform process may be pipelined through a series of dedicated hardware gates (instead of executed as a sequence of software instructions repeatedly loaded and processed by a general-purpose microprocessor).

The Image Processor 102 is not a stand-alone part but, instead, relies on the (Central) Processor 106 for control instructions. The Image Processor 102 sits on the Address and Data Buses and is accessible by the Processor 106 through a series of registers. In this manner, the Processor 106 may instruct the Image Processor 102 what to perform and when. For instance, the Processor 106 may instruct the Image Processor 102 to turn on the Sensor 101, to capture an image at the Sensor 101, and to execute the wavelet transform. Therefore, the Image Processor 102 is very much a facilitator but is not in and of itself a controller for the system.

The Shutter Actuator 103 is a simple, generic component for controlling light exposure on the Sensor 101. Depending on the behavior of the actual sensor employed, the Shutter Actuator 103 may not even be necessary. In particular, the Shutter Actuator 103 is employed in those instances where the Sensor 101 requires a black reference. In such an embodiment, the Shutter Actuator 103 is an electromechanical interface coupled to a solenoid which, when the interface responds to a particular logic level, triggers an open/close cycle of a mechanical shutter. The mechanical shutter, which serves to selectively block light entering the lens assembly of the camera, may be of a conventional design available from a variety of suppliers. A suitable supplier includes, for instance, Sunex, Inc. of Carlsbad, Calif.

The Image Memory (DRAM) 104 serves to store the image captured from the sensor. The Sensor 101 itself does not “store” the image that it captures. Therefore, the Image Memory 104 is an image capture and in-place transform (frame) buffer. This memory is controlled by the Image Processor 102 and can be shut off when not in use for power saving purposes. During basic operation of the camera, the captured image is transferred directly into the Image Memory 104, using a sample/transfer technique. In order to make this efficient, the process is controlled by the Image Processor 102 in a manner somewhat akin to DMA (direct memory access) transfer employed on desktop computers. Here, the Image Processor 102 functions as a state machine which simply samples and transfers information from the Sensor 101 to the Image Memory 104. In the presently-preferred embodiment, the Image Memory 104 comprises conventional DRAM (dynamic random-access memory) memory available from a variety of vendors, including, for instance, Toshiba, Micron, Hitachi, Samsung, and others. A size of about 4 MB (megabyte) or more is suitable for this component.

The next several components discussed, which may be viewed as components hanging off of the Address and Data Buses of the Processor 106, are typical components that one would ordinarily expect to find when implementing a data processing device; collectively, these components may be viewed as a computer embedded in the camera. For example, these components include the previously-mentioned general-purpose microprocessor (Processor 106) coupled to memory (System Memory 105 and Program Code Flash Memory 107). The Working or System Memory 105 is the general working or scratchpad memory for the Processor 106. This memory is used for storing program-created variables, stacks, heap(s), and the like. In the presently-preferred embodiment, the System Memory 105 comprises static RAM (e.g., SRAM), which is also available from a variety of vendors. A size of about 128 KB (kilobyte) or more is suitable for this purpose. The Program Code Flash Memory 107, on the other hand, comprises 1 MB of directly-addressable flash storage that holds the operating system and embedded software, that is, the program code comprising the instructions that the processor must execute to operate. The flash memory, which may be conventional flash memory that is available from a variety of vendors, need not be of the removable type, as the Program Code Flash Memory 107 is not intended to be removed from the system by the camera user.

The Processor 106 itself, in the presently-preferred embodiment, comprises a 32-bit RISC ARM Processor designed by ARM Limited of Maidenhead, UK. ARM licenses its designs to semiconductor partners for manufacture, supply, and support; for a list of ARM licensees, see e.g., http //www.arm.com/Partners/. The ARM processor has an efficient instruction set that is ideal for performing cyclical functions quite rapidly and includes sufficient bandwidth for transferring large amounts of data quickly (e.g., for performing Huffman coding on a large amount of data). Additionally, the processor is a dedicated processor, without the overhead of a substantial number of peripherals. These features make the processor attractive for use in a digital camera embodiment.

For a camera embodiment, the device will, in general, be expected to include an interface that is capable of receiving input from users. Keypad and Controls 108 are conventional inputs that support user input. Similarly, the Direct View Display (“Viewfinder”) 109 is a direct view LCD (liquid crystal display) that provides feedback to the user or camera operator. During photography mode, the Viewfinder 109 replaces the plastic viewfinders and LCD panels found on most digital cameras and provides the most accurate real-time representation of the scene visualized by the sensor. The Viewfinder 109 overlays simple icons onto the image to indicate the status of various camera settings. The Viewfinder 109 fits inside an eyepiece which keeps sunlight out and allows the operator to visualize the scene in any lighting conditions. During preview mode, the Viewfinder 109 shows previews of the captured photos and allows the operator to delete unwanted photos or tag photos for wireless transmission. Thus for a camera embodiment, the Viewfinder 109 is used to provide a representation of the image that is being captured, in preview and/or post-capture fashion.

In order to provide the display image to the Viewfinder 109, the Sensor 101 is subsampled at a rate to create a version of the image appropriate for display. During preview processing, the system continuously captures the sensor mosaic and sub-samples the resulting mosaic for preview purposes. A histogram of the sampled luminosity is fed into a “linearization” filter to produce a balanced dynamic range for best optical perception. The scaled and “linearized” image is then displayed on the viewfinder module. The histogram data is then adjusted to match the preview image for use in linearizing the next image. The cycle is repeated continuously to provide a real-time viewfinder mechanism. The Viewfinder 109 itself typically operates in conjunction with a display controller and a frame buffer (not shown), both of which may be integrated within the display component itself.

Both the Keypad and Controls and Display components, which may be conventional in nature, interface directly with the Processor 106 through general I/O (e.g., I/O Bus). Typically, such devices communicate with the microprocessor through means of interrupt requests (IRQ). Both the Keypad and Controls and Display components are available from a variety of vendors. Examples include Sharp, Toshiba, Citizen of Japan, Samsung of South Korea, and Hewlett-Packard of Palo Alto, Calif. More customized displays are available from Displaytech, Inc. of Longmont, Colo. For an embodiment that does not need to interact with users, such as a surveillance camera, the foregoing components may be eliminated.

Additionally for a camera embodiment, it is desirable for the device to include an interface for standard peripheral devices, such as a detachable flash device. This may be provided by Hot Shoe (Accessory) Interface 110, which is a general I/O port that may comprise a serial interface of a conventional design that the camera uses to interface to its accessories via the Hot Shoe Interface. In this manner, a flash accessory can be clipped onto the camera via the Hot Shoe Interface for added illumination.

The Hot Shoe Interface 110 combines a Serial Peripheral Interface (SPI) with a multiplexed I/O bus which provides a plug-and-play interface to a family of accessories. These accessories may include, in addition to a flash unit, a wireless holster for cellular (e.g., Motorola) phones, extra film backs for compatibility with format digital film (e.g., Sony Memory Stick or SmartMedia), a USB cradle, an RJ-11 modem cradle, a wireless cellular module, extender cables, and the like. In the currently-preferred embodiment, the interface is based on the I²C-standard serial interface, which supports logic allowing the device to sense I²C-compatible devices that are attached to the port. I²C, which stands for Inter IC Communication, is a serial bi-directional communication protocol created by Philips Semiconductor (subsidiary of Philips Electronics, based in The Netherlands) and is used for communication between integrated circuits. Most systems have one master and several slaves that communicate using only two wires. Every device has its own identification code. If that code is sent by the master only that device will respond with an acknowledgement. After the acknowledgement, the data to be communicated is sent or received by the master. Further information about the I²C communication protocol is available from Philips Electronics of The Netherlands. As with the Keypad and Controls 108 and Direct View Display or Viewfinder 109, the Hot Shoe Interface 110 itself is not required for implementing the image capturing and processing methodology of the present invention. In the specific embodiment of a consumer product such as a camera, though, these components typically would be included.

The system 100 includes Digital Film Flash Memory 111, which serves as the “digital film” for the system for storing compressed images. The Flash Memory 111 may comprise available flash memory removable media, such as CompactFlash, DataFlash, and Sony Memory Stick, typically in a 16 MB or larger size. Available vendors for flash memory include, for example, SanDisk of Sunnyvale, Calif. or Sony of Japan. Alternatively, the Flash Memory 111 may be affixed directly (i.e., non-removable) to the system 100. In such an embodiment, the additional bulk associated with a removable media cartridge holder and its accompanying interface may be avoided. Those skilled in the art will appreciate that the system 100 may incorporate other non-volatile memory configurations and designs that readily accommodate the image capture and processing methodology of the present invention. In general, for a consumer device embodiment, one should choose media that accommodates on the order of 100 compressed images or more.

The camera embodiment is powered by a single CR-123 lithium battery (not shown), provided with instant-on capability. Due in part to the distributed image processing approach of the present invention (presented below), the camera has significant power savings over other camera designs. This gives the device not only a size and weight advantage over other cameras but also a battery life advantage.

For connectivity, the system includes a wireless holster, a USB cradle, and a modem cradle. The wireless holster physically connects the camera to a cellular phone (e.g., Motorola cellular phone) and interfaces the Hot Shoe Interface to the phone's external accessory plug. The camera can be easily pulled out of the holster for use and clipped back in for transmission. Detection of the holster and phone signal is automatic to allow for hands-free transmission and there is no risk of corruption due to interruption by either loss of signal or unclipping. The camera clips into the USB cradle through the Accessory Hot-Shoe Interface 110 to provide rapid photo interchange to a personal computer equipped with a standard USB port. The USB cradle acts as a USB slave device and therefore requires no batteries or power supply for operation and instead draws its power from the PC. The camera can also clip into a modem cradle through the Hot Shoe Interface. The modem cradle allows the camera to transmit images to a PhotoServer module (operating on system 150, described below) via a land line connection (e.g., 33.6 KBps) via a standard RJ-11 phone jack. The modem cradle is powered by the battery in the camera.

The specifications for the currently-preferred camera embodiment may be summarized as follows.

TABLE 1 Miniature Wireless Digital Camera Specifications: Sensor: 1.3 Mega-Pixel Color CMOS Optics: 18 mm Fixed Focal Length, Fixed Aperture Exposure Control: Automatic, Macro Mode, Indoor/Outdoor Mode Processor: ARM 32-bit RISC Chipset: Image Processor (Lightsurf PhotonOne) Memory: 4 Mbytes DRAM + 128 Kbytes SRAM Digital Film: 16 Mbytes Internal Flash Film File Format: Progressive Photograph Format (PPF) Wireless Protocol: Communication protocol, such as packet-based TCP/IP, WAP, or the like Battery: CR-123 Accessory Interface: Accessory Hot-Shoe Accessories: Flash Unit, Extra Film Back, Motorola Cellular Holster, USB Cradle, Modem Cradle

B. Basic Computer Hardware (e.g., for computers that may “host” add-on devices)

Portions of the present invention may be implemented on a conventional or general-purpose computer system, such as an IBM-compatible personal computer (PC) or server computer that may host the above-described digital camera device (e.g., via USB or RS-232 connectivity). FIG. 1B is a very general block diagram of an IBM-compatible system 150. As shown, system 150 comprises a central processor unit(s) (CPU) 151 coupled to a random-access memory (RAM) 152, a read-only memory (ROM) 153, a keyboard 156, a pointing device 158, a display or video adapter 154 connected to a display device 155, a removable (mass) storage device 165 (e.g., floppy disk), a fixed (mass) storage device 166 (e.g., hard disk), a communication port(s) or interface(s) 160, a modem 162, and a network interface card (NIC) or controller 161 (e.g., Ethernet). Although not shown separately, a real-time system clock is included with the system 150, in a conventional manner.

CPU 151 comprises a processor of the Intel Pentium® family of microprocessors. However, any other suitable microprocessor or microcomputer may be utilized for implementing the present invention. The CPU 151 communicates with other components of the system via a bi-directional system bus (including any necessary I/O controller circuitry and other “glue” logic). The bus, which includes address lines for addressing system memory, provides data transfer between and among the various components. Description of Pentium-class microprocessors and their instruction set, bus architecture, and control lines is available from Intel Corporation of Santa Clara, Calif. Random-access memory 152 serves as the working memory for the CPU 151. In a typical configuration, RAM of sixteen megabytes or more is employed. More or less memory may be used without departing from the scope of the present invention. The read-only memory (ROM) 153 contains the basic input/output system code (BIOS)—a set of low-level routines in the ROM that application programs and the operating systems can use to interact with the hardware, including reading characters from the keyboard, outputting characters to printers, and so forth.

Mass storage devices 165, 166 provide persistent storage on fixed and removable media, such as magnetic, optical or magnetic-optical storage systems, flash memory, or any other available mass storage technology. The mass storage may be shared on a network, or it may be a dedicated mass storage. As shown in FIG. 1B, fixed storage 166 stores a body of program and data for directing operation of the computer system, including an operating system, user application programs, driver and other support files, as well as other data files of all sorts. Typically, the fixed storage 166 serves as the main hard disk for the system and stores application software implementing a PhotoServer component (PhotoDesktop, when implemented on a desktop computer), which may operate to process images uploaded from digital cameras (e.g., digital camera device 100).

In basic operation, program logic (including that which implements methodology of the present invention described below) is loaded from the storage device or mass (fixed) storage 166 into the main (RAM) memory 152, for execution by the CPU 151. During operation of the program logic, the system 150 accepts user input from a keyboard 156 and pointing device 158, as well as speech-based input from a voice recognition system (not shown). The keyboard 156 permits selection of application programs, entry of keyboard-based input or data, and selection and manipulation of individual data objects displayed on the display device or screen 155. Likewise, the pointing device 158, such as a mouse, track ball, pen device, or the like, permits selection and manipulation of objects on the display screen. In this manner, these input devices support manual user input for any process running on the system.

The computer system displays text and/or graphic images and other data on the display device 155. Display device 155 is driven by the video adapter 154, which is interposed between the display device 155 and the system. The video adapter 154, which includes video memory accessible to the CPU, provides circuitry that converts pixel data stored in the video memory to a raster signal suitable for use by a cathode ray tube (CRT) raster or liquid crystal display (LCD) monitor. A hard copy of the displayed information, or other information within the system 150, may be obtained from the printer 157, or other output device. The printer 157 may include, for instance, an HP LaserJet® printer (available from Hewlett-Packard of Palo Alto, Calif.), for creating hard copy images of output of the system.

The system itself communicates with other devices (e.g., other computers) via the network interface card (NIC) 161 connected to a network (e.g., Ethernet network), and/or a modem 162 (e.g., 56 K baud, ISDN, DSL, or cable modem), examples of which are available from 3Com of Santa Clara, Calif. The system 150 may also communicate with local occasionally-connected devices (e.g., serial cable-linked devices) via the communication (“comm”) interface 160, which may include an RS-232 serial port, a Universal Serial Bus (USB) interface, or the like. Devices that will be commonly connected locally to the comm interface 160 include laptop computers, handheld organizers, digital cameras, and the like.

IBM-compatible personal computers and server computers are available from a variety of vendors. Representative vendors include Dell Computers of Round Rock, Tex., Compaq Computers of Houston, Tex., and IBM of Armonk, N.Y. Other suitable computers include Apple-compatible computers (e.g., Macintosh), which are available from Apple Computer of Cupertino, Calif., and Sun Solaris workstations, which are available from Sun Microsystems of Mountain View, Calif.

The above-described system 150 is presented for purposes of illustrating the basic hardware underlying desktop and server computer components—“host” components—that may be employed in the system of the present invention. For purposes of discussion, the following description will present examples in which it will be assumed that there exists a “host” device which is to host a client device. The present invention, however, is not limited to any particular environment or device configuration. In particular, a client/host distinction is not necessary to the invention, but is used to provide a framework for discussion. Instead, the present invention may be implemented in any type of computer system or processing environment capable of supporting the methodologies of the present invention presented in detail below.

C. Basic System Software

Illustrated in FIG. 2, a computer software system 200 is provided for directing the operation of the computer system 150. Software system 200, which is stored in system memory (RAM) 152 and on fixed storage (e.g., hard disk) 166, includes a kernel or operating system (OS) 210. The OS 210 manages low-level aspects of computer operation, including managing execution of processes, memory allocation, file input and output (I/O), and device I/O. One or more application programs, such as client application software or “programs” 201 (e.g., 201 a, 201 b, 201 c, 201 d), including image processing software, may be “loaded” (i.e., transferred from fixed storage 166 into memory (RAM) 152) for execution by the system 150.

Software system 200 includes a graphical user interface (GUI) 215, for receiving user commands and data in a graphical (e.g., “point-and-click”) fashion. These inputs, in turn, may be acted upon by the system 150 in accordance with instructions from operating system 210, and/or client application module(s) 201. The GUI 215 also serves to display the results of operation from the OS 210 and application(s) 201, whereupon the user may supply additional inputs or terminate the session. Typically, the OS 210 operates in conjunction with device drivers 220 (e.g., “Winsock” driver) and the system BIOS microcode 230 (i.e., ROM-based microcode), particularly when interfacing with peripheral devices. OS 210 can be provided by a conventional operating system, such as Microsoft® Windows 9x, Microsoft® Windows NT, or Microsoft® Windows 2000, all available from Microsoft Corporation of Redmond, Wash. Alternatively, OS 210 can also be an alternative operating system, such as IBM OS/2 (available from IBM of Armonk, N.Y.) or Macintosh OS (available from Apple Computer of Cupertino, Calif.).

The following description focuses on an application/driver “uploader” system of the present invention implemented in a first device (e.g., system 100 described above), thereby allowing that device to inject an object (e.g., application or driver) into a second device (e.g., system 150 described above). The uploader system, when implemented in system 100, is a software-implemented system stored in Program Code Flash Memory 107 for execution by Processor 106, after a loading into System Memory 105. If desired, however, the application/driver “uploader” system of the present invention may be implemented in an ASIC (application-specific integrated circuit). The application/driver to be injected will reside in module 111 or module 107 of FIG. 1A. The communications (TCP/IP or PPP) would occur through module 110 of FIG. 1A or through a COMM INTERFACE from the 32-Bit RISC ARM processor (this would be a module such as 160 on FIG. 1B attached to the ARM processor). The COMM interface would typically include an RS-232 UART (Universal Asynchronous Receiver Transmitter) module.

Application/driver “uploader” system providing methodology for dynamic uploading and execution of applications and drivers between connected devices

A. Introduction

The following description will present examples in which it will be assumed that there exists a first device that is to be connected to a second device(s), such as a digital camera device (e.g., system 100) connected to a computing device (e.g., computer system 150). To simplify the description, one device will be referred to as a “client” device and the other device will be referred to as a “host” device. For instance, in describing the digital camera embodiment below, the digital camera device is considered the “client” device and the device(s) that the digital camera device connects to is considered the “host” device(s). As previously discussed, a client or host distinction is neither necessary to the invention nor even necessarily desirable, but merely provides a framework for discussion. The focus of the following description, therefore, is not focused on a particular hardware configuration. Not only may the present invention be applied to a variety of disparate configurations, but in fact the present invention is most advantageous when applied to disparate configurations. The following description will focus on the application of dialog and negotiation among two or more devices, in accordance with the present invention. The devices themselves, however, may be configured in a variety of hardware configurations (e.g., according to the particular needs of the user and/or vendor). Thus, the following description is for the purposes of illustration and not limitation.

B. Design Considerations

In accordance with the present invention, the following approach is adopted for supporting the dynamic uploading and execution of applications and drivers between (temporarily or permanently) connected devices. The device which is to be hosted (e.g., the “client” device) initially probes its environment to determine which device or devices it is attached to (e.g., the “host” device(s)). Once it has correctly discerned the relevant host or target device(s), the client device includes the capability of immediately sending out (i.e., uploading) a particular driver or application (i.e., object or file of interest) for placement, and ultimately execution, at the host device. Once the particular object or file of interest has been “injected” into the host device and is executing, the client device may simply revert to a “listening mode” in which it waits to be told what to do (i.e., receive commands from the application or driver which is now executing at the host device).

This approach is particularly well-suited for devices which serve as “add-on” devices (clients) to other devices (hosts) that are “smarter,” for instance, including more processing capability and/or memory. In this scenario, the client device enters into a dialog with a device with more resources for the purposes of harnessing the resources of the host device for operating the client or add-on device. The client device is, using this approach, able to start running (i.e., driver-directed operation) immediately upon attachment to a host device that can be identified.

Against this backdrop, one must remain cognizant of the constraints presented by existing devices. One must take into account the need for backwards compatibility, including wireline, as well as wireless, compatibility, so that a particular approach does not lock out any particular class of devices. By the same token, the approach should provide forward compatibility, so that the approach is prepared for future devices. Therefore, the approach adopted by the present invention is designed to be easily extended to support multiple host devices as well as multiple communication media. Upon probing its environment, the client device identifies all relevant host devices over all relevant communication media. Then, the client device enters into a dialog with each particular host device. In a manner similar to that described above for a single host device, the client device uploads appropriate application or driver software, as appropriate, for each identified host device. Upon entering the listening mode, the client device can respond to any and all requests from the multiple host devices.

For purposes of backward and forward compatibility, the preferred embodiment of the present invention supports TCP/IP protocol. “TCP/IP” or “Transmission Control Protocol/Internet Protocol” is the suite of communications protocols used to connect devices on the Internet. TCP/IP uses several protocols, the two main ones being TCP and IP. TCP enables two hosts to establish a connection and exchange streams of data. The protocol guarantees delivery of data and also guarantees that packets will be delivered in the same order in which they were sent. IP protocol, on the other hand, deals only with packets—that is, the individual pieces of a message transmitted over a packet-switching network. TCP/IP is built into the UNIX operating system and is used by the Internet, making it the de facto standard for transmitting data over networks. Because TCP/IP has widespread support and can also run over many different types of physical connections, it is adopted as the preferred connectivity protocol in the preferred embodiment. In this manner, the preferred embodiment can leverage the pre-existing low-level protocols that are already supported by a multitude of devices.

In addition to TCP/IP, the present invention embraces a file-based approach to object storage and handling. A “file” is a collection of data or information that has a name, or “file name.” Common examples of files include executable files which contain program commands in an executable format, text files which contain human-readable textual data, and binary files which contain data or instructions in binary format. A file-based technique is a well-known method for storing and transmitting information, including applications and drivers. Therefore, in the preferred embodiment, a file-based approach is adopted, including use of common file names, which are portable across a variety of different systems.

C. General System Modules

FIG. 3 is a high-level block diagram illustrating an application/driver “uploader” system of the present invention. As described above, the system 300 includes software modules that, in a preferred embodiment, are software or ASIC (application-specific integrated circuit) modules implemented on one device (e.g., digital camera device or system 100) that is to be connected to another (host) device (e.g., computing device or system 150).

The core engine or workhorse module for the system 300 is in the application/driver uploader (engine) module 311. This module serves to determine what is the device(s) (i.e., host(s)) that the current device (i.e., client) is connected to. Based on this determination, the module is also responsible for coordinating the activities of (1) initiating a communication session with the host(s), (2) uploading the actual object of interest (e.g., driver or application file) onto the host device, (3) invoking execution of that object, and (4) properly terminating the communication session, as desired.

The application/driver uploader module 311 coexists with another high-level module, the command server module 315. Once the uploader module 311 has completed its overall task of injecting an application or driver of interest, the command server module 315 serves to wait for requests/commands from the particular application or driver and that has just been uploaded to the host device(s), so that the client device itself may operate under control of the host device(s), namely, operating in response to a given command issued from a driver executing at the host device(s).

To support the just-described high-level functionality of the uploader module 311 and the command server module 315, the system 300 includes lower-level modules. Therefore, at the next to lower-level, the system 300 includes a PHY (physical) manager 321. This module serves as an “identifier” supporting module for the uploader module 311. In particular, the PHY manager 321 determines which specific device (i.e., host(s)) is physically connected to the client device, at a given point in time (e.g., upon first connect). Here, the PHY manager 321 is responsible for the initial physical connection, be it wireline or wireless. In operation, the PHY manager 321 sets various internal flags for indicating which host device(s) it has uncovered as being physically connected to the client device. These flags are reflected in a registry 333, which is a repository or database storing configuration information. Other modules of the system 300, including the uploader module 311, may extract information from the registry 333 to determine what flags have been set by the PHY manager 321, for determining which host devices are currently connected. The particular host-specific steps required for uploading a driver of interest to the host device may be discerned based on the flags set by the PHY manager 321.

The uploader module 311 and the command server module 315 also employ an XML parser 323. The XML parser 323 provides an internal communication protocol for issuing commands and transmitting data. In the currently-preferred embodiment, all of the commands and accompanying data transmitted (e.g., from driver to client device, or vice versa) are packaged using XML syntax, which provides an extensible tag-based approach to wrappering data. “XML” or “Extensible Markup Language” is a specification developed by the World Wide Web Consortium, an international consortium of companies involved with the Internet and the Web. XML is a pared-down version of SGML (Standard Generalized Markup Language), which is designed especially for Web documents. It allows designers to create their own customized tags, enabling the definition, transmission, validation, and interpretation of data between applications and between organizations. For further description of XML, see, e.g., Extensible Markup Language (XML) 1.0 specification which is available from the World Wide Web Consortium (www.w3.org), the disclosure of which is hereby incorporated by reference. The specification is also currently available on the Internet at http://www.w3.org/TR/REC-xml.

The following two command and response pairs are examples of the XML syntax.

Command: Load Application <LoadApp> <name>Application Name</name> <bin> <size>1234</size> (binary data here) </bin> </LoadApp> Response: Load Application <LoadAppR> <status>0</status> <handle>5678</handle> </LoadAppR> Command: Activate Application <ActivateApp> <handle>5678</handle> <priority>1</priority> </ActivateApp> Response: Activate Application <AcxtivateAppR> <status>0</status> </ActivateAppR> As shown, XML may be used to provide tag-delimited commands and associated data.

As an additional advantage, XML syntax is supported by a variety of high-level servers. As it can be expected that client devices will often interact with servers across the Internet, XML serves as a “glue” logic supporting communication between these devices. By adopting XML syntax, a given client device may communicate with a high-level server in a more efficient manner, as XML-wrappered data may be transmitted between devices without the need to be converted or translated before transmission.

Also at the level of the XML parser 323, the system 300 includes a TCP/IP stack 325 (i.e., implementing the protocol layers that define communication over the Internet). This module allows the use of standard TCP and IP protocols, thereby providing a socket-based communication interface that is highly compliant with available operating systems (e.g., UNIX, Windows, Linux, Macintosh, PalmOS, and the like) across multiple hardware platforms. By adopting TCP/IP, the client device can leverage existing connectivity protocols that are commonly found on most devices. In the currently-preferred embodiment, the TCP/IP stack 325 is provided as InterNiche Portable TCP/IP Protocol Stack, version 1.6, available from InterNiche Technologies, Inc. of San Jose, Calif. (a data sheet is currently available at http://www.iniche.com/download/datasheets.htm).

At the next to lower level, the system 300 includes a registry manager 331 which stores state information for the system 300 in a registry 333. Recall that the PHY manager 321 sets various status flags, for defining the current environment that the client device is connected to. The flags are maintained as name/value pairs (e.g., Windows-like registry settings) in the registry 333, under control of the registry manager 331. The registry 333 comprises a hierarchically-organized “tree” of “keys” (i.e., intermediate nodes) and “values” (i.e., leaf modes consisting of name/value pairs that may be defined). Within the registry 333, certain keys at the root of the hierarchy are considered well-known and provide primary division of the tree. Intermediate keys are used to further organize the registry; the very existence of certain of these intermediate nodes has semantic meaning. The leaf nodes, i.e., “named values”, are the primary items of focus. In this manner, the registry 333 serves as a repository indicating what various configuration settings, such as TCP/IP configuration settings, that are required to be set in order to communicate with a particular host device.

The registry implementation in the currently-preferred embodiment supports named-value leaves of the following types:

-   -   (1) UI32, which is 32-bit unsigned data. Some or all of these 32         bits may be used and/or interpreted as seen fit by the software         using the registry, e.g., these 32 bits might be treated as a         signed 32-bit value, or perhaps, an unsigned 8-bit value, or the         like.     -   (2) ASCII strings, which are 8 bits/character ASCII, terminated         by the “null character”, ‘0’.     -   (3) UNICODE strings, which are 16 bits/char Unicode, terminated         by the “Unicode null character”, L‘0’.     -   (4) Arbitrary 8-bit binary data, the length of which is stored         by the registry implementation.

The registry supports keys and named values, some of which are “permanent” and some of which are “transient”. Permanent keys are stored in client devices in such a way that they “survive” between active power-on sessions. They are implemented in such a way that they are extremely durable over/through the most “user-abusive” (e.g., unplanned) power-downs. Transient keys are only maintained for a single power-on session. They are typically few in number, and are most often seen marking “current” states/preferences. Additionally, the registry may define certain keys and values to be “read-only”.

The system 300 includes its own a file system 335. This allows the system 300 to store its own applications, data, and other binary information. In the currently-preferred embodiment, this is implemented as a DOS-like (e.g., MS-DOS) or UNIX-like file system, for providing local storage on the client device. The file system 335 may be supplied by a real-time operating system, such as a digital camera operating system; or, alternatively, it may be supplied as a stand-alone subsystem, independent of the underlying operating system. In the currently-preferred embodiment, the file system 335 is USFiles® File System (version 3.00.02), available from U.S. Software of Hillsboro, Oreg.

To support nonvolatile flash memory storage, the file system 335 may work in conjunction with a lower-level module, the flash manager 345 (or other persistent storage media, such as hard disk in). The flash manager 345 includes logic appropriate for converting file information into a format appropriate for nonvolatile storage. In particular, in the preferred embodiment, it is desirable to store application drivers and related information in flash memory. Thus, the flash manager 345 serves as a module for managing the hardware resources available for storing files.

Finally, the system 300 includes a real-time operating system 341. Operating systems, which perform basic system tasks, provide an interrupt-driven mechanism for servicing system-level requests. In the currently-preferred embodiment, the real-time operating system is provided by the eCos operating system (Version 1.2.1), provided by Red Hat, Inc. of Durham, N.C. Version 1.3.1 is also available.

D. Detailed Description of Registry

The registry defines a registry key for characterizing communication and connectivity to host device(s), the CONNECT/commdev key, as follows.

Key: CONNECT/commdev Type: Key Persistent: Yes Application Access: Read-only Maintenance Server Access: Read/Write/Create/Delete Sub-keys are specified to provide the client device with specific connectivity option information. In particular, the connectivity management function of a client device uses the existence of sub-keys of CONNECT as a “table” of possible communicating devices that may be connected from time-to-time to the client device. This connectivity management function monitors for the attachment (or “arrival”) of the devices described by these sub-keys. For example, a client camera device may be designed for connection to a XYZ Corp. USB cradle and a XYZ Corp. model 560 cellular telephone. In this case, there might be sub-keys, CONNECT/XyzUsbCradle and CONNECT/XyzCell560, defined. Server maintenance access provides access to certain keys and values from “remote servers” via a secure communications protocol. This access allows for post-factory configuration and/or “final user” (re)provisioning of client devices.

Under foregoing sub-keys additional keys, as described below, provide necessary information to the client device on how to detect the attachment of one of these devices and, after having detected such devices, how to utilize the possible connectivity these devices may provide.

Key: CONNECT/commdev/PHY Type: Key Persistent: Yes Application Access: Read-only Maintenance Server Access: Read/Write/Create/Delete

This sub-key of the CONNECT/commdev key provides the client device with information germane to the detection of the attachment of the commdev. This attachment is detected using a response-matching approach, where a certain sequence of data is transmitted on the client's physical communications link and then responses to each are compared against known responses for a commdev. The sub-keys CONNECT/commdev/PHY/QUERY and CONNECT/commdev/PHYIRESPONSE organize these queries/responses.

Key: CONNECT/commdev/PHY/QUERY Type: Key Persistent: Yes Application Access: Read-only Maintenance Server Access: Read/Write/Create/Delete

This sub-key of a key CONNECT/commdev/PHY organizes the queries needed to “sense” the attachment of commdev.

Values: CONNECT/commdev/PHY/QUERY/n Type: BINARY Persistent: Yes Application Access: Read-only Maintenance Server Access: Read/Write/Create/Delete

These values are individual query-byte sequences used in the “sensing” of commdev. Each is ordered from 0 upward. The query-byte sequences are output to “sense” possible attachment of commdev. Normally, for each value CONNECT/commdev/PHY/QUERY/n, there is usually a corresponding value CONNECT/commdev/PHY/RESPONSE/n. If there is no such corresponding value, or the value is zero length, then the “match” is “instantaneous”; the client device then proceeds to the next, if any, query/response pair.

Key: CONNECT/commdev/PHY/RESPONSE Type: Key Persistent: Yes Application Access: Read-only Maintenance Server Access: ReadlWrite/Create/Delete

This sub-key of a key CONNECT/commdev/PHY organizes the responses needed to “sense” the attachment of commdev.

Values: CONNECT/commdev/PHY/RESPONSE/n Type: BINARY Persistent: Yes Application Access: Read-only Maintenance Server Access: Read/Write/Create/Delete

These values are individual response-byte sequences used in the “sensing” of commdev. Each is ordered from 0 upward. The response-byte sequences are looked for after the output of a query-byte sequence to “sense” possible attachment of commdev.

Value: CONNECT/commdev/PHY/Id Type: UI32 Persistent: Yes Application Access: Read-only Maintenance Server Access: Read/Write/Create/Delete

This UI32 value is used to uniquely identify a commdev. The client device vendor administers this “global numberspace”, assigning a range of numbers to client device technology licensees. These licensees use them in their implementations to identify the variety of connectivity-providing devices that their client devices sense/support.

Value: CONNECT/commdev/PHY/EffectiveBaud Type: UI32 Persistent: Yes Application Access: Read-only Maintenance Server Access: Read/Write/Create/Delete

This UI32 value is used to indicate the approximate expected, effective speed in bytes/second of a commdev's raw data channel. This attempts to provide a speed metric based on information known a priori about the underlying “data service” a commdev typically can provide.

Value: CONNECT/commdev/PHY/Cost Type: UI32 Persistent: Yes Application Access: Read-only Maintenance Server Access: Read/Write/Create/Delete

This UI32 value is used as a BYTE, where 0 is the “lowest cost” and 255 is the “highest cost”. This “cost” indicates how “cheap” the commdev's physical bearer is, i.e., there is no (or an extremely trivial) “per minute” cost to use the communications facility. This attempts to provide a “generic” cost metric that may be used by certain client devices to aid in the implementation of possible user preferences regarding issues such as quality of images uploaded over different “cost” links.

In the registry, a CONNECT/CURR/PPP key is used to track certain current run-time data, related to the client device's PPP link. The below-listed subkey values may be stored.

Value: CONNECT/CURR/PPP/IpAddrLocal Type: UI32 Persistent: No Application Access: Read/Write/Create/Delete Maintenance Server Access: Read-only This value is the client device's current IP address in “network order”. If the value is 0×00000000, it may be assumed that the client device has not been able to obtain an IP address. The client device application software, specifically the connectivity management function, creates and writes/maintains this value.

Value: CONNECT/CURR/PPP/IpAddrRemote Type: UI32 Persistent: No Application Access: Read/Write/Create/Delete Maintenance Server Access: Read-only This value is the far peer device's current IP address in “network order”. Typically, this would not be the client-supporting server, but rather the Internet host with which the current PPP link is established. If the value is 0×00000000, it may be assumed that the client device has not been able to obtain an IP address. The client device application software, specifically the connectivity management function, creates and writes/maintains this value.

Value: CONNECT/CURR/PPP/Mtu Type: UI32 Persistent: No Application Access: Read/Write/Create/Delete Maintenance Server Access: Read-only

This value is the negotiated PPP Maximum Transmission Unit (MTU) for the currently established PPP link. If there is no established PPP link, this value should be 0. The client device application software, specifically the connectivity management function, creates and writes/maintains this value. Currently, this is not a required value. The client device should not create and/or maintain this value.

A CONNECT/commdev/NET key is used to organize parametric information related to Internet communications, for layers above PPP.

Value: CONNECT/commdev/NET/Dns Type: Key Persistent: Yes Application Access: Read-only Maintenance Server Access: Read/Write/Create/Delete

This key organizes the specification of zero, one, or more Domain Name Server machines on the Internet, which should be used by the IP stack to resolve fully-qualified host names. If this sub-key is not present, it is to be interpreted that no DNS services are needed in the communication configuration specified by CONNECT/commdev. If this key exists but has no values (specifying DNS IP addresses), the system interpretes this to indicate that DNS information is required and that it should be obtained using DHCP.

Value: CONNECT/commdev/NET/Dns/n Type: CLsStr Persistent: Yes Application Access: Read-only Maintenance Server Access: Read/Write/Create/Delete

This/these values, 0 thru n, are value data (CLsStr data) that specify the IP address (in “dot form” address, e.g., “204.30.31.5”) of a Domain Name Server (DNS) that the client device should preferably use in mapping host names to IP addresses. These values only exist in the communications environment described by CONNECT/commdev only if the DNS address(es) must be specified a priori, e.g., there is no dynamic DNS information available during PPP establishment time.

Value: CONNECT/commdev/NET/TcpMss Type: UI32 Persistent: Yes Application Access: Read-only Maintenance Server Access: Read/Write/Create/Delete

This UI32 value is the maximum size of a TCP transmission segment.

Value: CONNECT/commdev/NET/TcpWindow Type: UI32 Persistent: Yes Application Access: Read-only Maintenance Server Access: Read/Write/Create/Delete

This UI32 value is the size of the TCP window in bytes.

Value: CONNECT/commdev/NET/TcpKeepAlive Type: UI32 Persistent: Yes Application Access: Read-only Maintenance Server Access: Read/Write/Create/Delete

This UI32 value is used as a BOOL, where 0 is FALSE and 1 is TRUE. A value of 1 indicates that the client device will generate “idle” TCP PDUs to keep any TCP connections up.

E. Detailed Description of PHY Manager

The PHY manager 321 will now be described in further detail. The PHY manager 321 probes for new devices over what the registry 333 lists as the then-current communication medium. Communication media may include, for instance, wireless, serial (RS-232)wired, USB, or the like. Depending on the hardware configuration of the client device, it is possible to have multiple communication media active simultaneously. Typically, the registry 333 includes a default (factory preset) configuration registry entry specifying the initial communication medium (or media) available upon initial power up of the client device. For this default connectivity entry and other connectivity entries, the registry 333 includes corresponding default communication rates (baud rates) and corresponding handshake protocols (command set). Using this information, the PHY manager 321 may execute an initial sequence of handshake commands and comparing any response received to a list of known responses for identifying a particular host device. For example, to elicit devices that may be connected via RS-232, the PHY manager 321 may begin by sending out corresponding sequences of initialization commands (e.g., AT commands), at different baud, for eliciting a response from any potential host that is connected. Probing for host devices continues until all known potential host devices have been enumerated. Based on what is found, the PHY manager 321 updates the registry 333 with information describing which host devices the client device is currently connected to.

In order to illustrate how the PHY manager 321 determines what host device(s) is connected to the device under use, consider the following two examples which illustrate the process used to determine if a host is connected. Both examples will use a serial RS-232 connection to transmit data.

EXAMPLE #1 Windows NT RRAS Server

This connection is set to emulate a serial port-to-serial port PC-to-PC connection. The first item is to set the serial port to the proper data rate. For this case, 115200 baud is the default. The next step is to send out a text string to the PC RAS Host. The following is the transmission and reply for a connection session.

Send: CLIENT [carriage-return] Reply: SERVER [carriage-return] Now, the process may negotiate a PPP connection with the Windows NT Server. PPP refers to Point-to-Point Protocol, a well-known method for transmission of IP packets over serial lines; see, e.g., RFC 1661: The Point-to-Point Protocol (PPP), available from the Network Working Group, the disclosure of which is hereby incorporated by reference. RFC 1661 is currently available via the Internet at: http://www.freesoft.org/CIE/RFC/1661/index.htm.

EXAMPLE #2 Modem mode of Cell Phone with internal PPP Server

This mode emulates a standard modem AT connection. For this case, the default serial port rate is 38400 baud. The following characters are sent on the serial port to determine that a modem-compatible device is connected.

Send: AT [carriage-return] Reply: OK [carriage-return] The next step is to negotiate a PPP session with the internal PPP Server. Refer to the above-mentioned RFC 1661 for more information on negotiating a PPP session.

The PHY manager 321 is also responsible for ensuring that any other low-level connectivity is met such that a state of TCP/IP communication is reached. This is required because TCP/IP may not in fact be operating at the point when the client device first initiates communication. For instance, in normal RS-232 serial communication and USB communication, TCP/IP will not yet be running. Although TCP/IP configuration may not be yet running at the outset, Point-to-Point Protocol (PPP) may be employed to ensure TCP/IP connectivity, in a manner similar to that commonly done with dial-up Internet connections. PPP (Point-to-Point Protocol), as described above, is a protocol defined in RFC 1661 for communication between two computers using a serial interface, such as a personal computer connected by phone line to a server. For example, Internet Server Providers typically provide their users with a PPP connection so that the provider's server can respond to user requests, pass them on to the Internet, and forward requested Internet responses back to the users.

Use of PPP is made possible due to the fact that most hosts that support a TCP/IP stack will also support PPP within their TCP/IP stack. Accordingly, the client device can initiate a PPP session through well-known means, and thereupon request TCP/IP communication. Additionally, the client device is also capable of being a PPP server, and thereby accepting clients as well. All told, through use of the available PPP protocol, the client device can initiate TCP/IP connectivity, including determining an IP address for a given host device, even if TCP/IP connectivity does not exist at the outset. In this manner, the PHY manager 321 sets up a communication TCP/IP channel allowing the client device to communicate with the connected host device(s).

F. Detail Description of Application/Driver Uploader Module

The application/driver uploader module 311 will now be described in further detail. This module acts on the information elicited by the PHY manager 321, as maintained in the registry 333, in order to determine what tasks need to be performed, in regards to interoperating with host devices. Within the TCP/IP parameters stored for a given host, the registry 333 will maintain an IP address for that host. In the currently-preferred embodiment, the client device communicates as a TCP/IP client, not as a server. A port (logical connection) number is defined for the host device to listen on.

Once a TCP/IP communication session is open, the application driver may now be “injected” into the host device. Now, the client device opens the corresponding file that contains the appropriate application driver (file). This request is serviced by the file system 335. If the appropriate application driver exists and can be opened, the file system 335 returns a file handle to the application/driver uploader 311. The application/driver uploader 311 may now package the file for transmission across the established TCP/IP communication medium. In the currently-preferred embodiment, this is accomplished by a defined internal command sequence. At the conclusion of this portion of the process, the file of interest has been injected into the host device, with a corresponding file handle returned to the client device.

The file handle returned to the client supports important client-controlled functionality, thereby allowing the client device to access the file that has just been injected into the host device in a variety of ways. For example, returning this file handle to the client device will allow the client device to perform a variety of operations on that file as it resides at the host device, including starting up the file as an application or driver. In the currently-preferred embodiment, the file handle returned to the client device is any reference to that application which is supported by the host device's architecture. This may be, for instance, a file handle provided by the host device or a file name recognized by the host device.

The final step of the process is to actually invoke execution of the injected application or driver. In this particular injection scenario, therefore, the injected object is an executable file (or capable of triggering execution of a corresponding executable file). Therefore, it includes program code, for instance, machine instructions for a particular target processor or byte code instructions for a virtual machine (e.g., Java byte code instructions for executing a Java virtual machine at the host). Java is a well-known programming language specification, available from Sun Microsystems of Mountain View, Calif. Further description of the Java Language environment can be found in the technical, trade, and patent literature; see e.g., Gosling, J. et al., The Java Language Environment: A White Paper, Sun Microsystems Computer Company, October 1995, the disclosure of which is hereby incorporated by reference.

In the instance where the injected application or driver comprises byte code (e.g., Java byte code), that application or driver may target a potentially larger number of host devices (compared to a processor-specific executable, which supports a smaller number of potential host devices). Therefore, in the currently-preferred embodiment, the application or driver to be injected comprises a Java program, with the intended host, in a corresponding manner, supporting run-time operation of a corresponding virtual machine capable of executing the program byte code (e.g., Java Virtual Machine at the host device capable of executing the Java program code). Although use of Java for creating the application or driver allows one to potentially target a larger number of host devices, those skilled in the art will appreciate that the methodology of the present invention is equally applicable to client-to-host object injection in both byte code and native machine code-supported environments.

To invoke execution, the client device issues a command which, when received by the host device, triggers execution of the just-injected application or driver. Based on the prior identification of the host device, the uploader 311 may retrieve from the registry 333 information indicating the appropriate command to issue for the identified host device. In the straightforward case, the host device may simply be instructed to begin execution of the injected application or driver. For some host devices, however, execution may have to be triggered through indirect means. For example, if the host device does not support direct execution of the injected application or driver, it may be possible to achieve the same result by instructing the host device to “restart” itself, whereupon the injected application or driver is recognized by the host device as an object that should be invoked (i.e., so that the host device starts up with the injected application or driver running). Once the injected application or driver is executing, it is able to direct operation of the host device, including having the host device issue appropriate commands to the client device for achieving a desired task (e.g., uploading photographs for wireless transmission).

Invocation of execution at the host device is perhaps best illustrated by way of example. The following example presents a command sequence illustrating invocation of an injected application or driver at a host device supporting the Java environment (i.e., including the Java Virtual Machine).

EXAMPLE #1 Java Environment

The following commands will start an application in the host device's Java environment:

Command: LoadApplication LoadApp(name = MyApp, size = (appsize), data = (binary application data)) Reply: LoadAppR(status = (pass/fail), handle = AppHand)) Command: StartApplication StartApp (handle = AppHand) Reply: StartApp(status = (pass/fail)) As result of this command sequence, the injected application is now running on the host device's Java Virtual Machine.

EXAMPLE #2 Palm Environment

The following command sequence will load an application into a Palm device.

Command: LoadApplication LoadApp(name = MyApp, size = (appsize), data = (binary application data)) Reply: LoadAppR(status = (pass/fail), handle = AppHand)) The user will need to manually run the application as a normal Palm application to begin using the application. Future versions of Palm-compatible devices may allow automatic execution, as the above Java environment.

G. Summary of Overall Operation

Referring now to FIGS. 4A-B, the overall method or process of the present invention may be summarized by the following method steps. As shown at step 401, the process gets underway upon the establishment of a connection (wireless or wireline) between a client device and a host device; the connection may be permanent or temporary. At step 402, starting with default registry information, the client device probes for any host devices. As described, this task falls specifically on the PHY manager. Based on the information uncovered at step 402, the registry (i.e., registry 333 above) is updated, at step 403, with information describing discovered host devices and corresponding communication information relevant to each such discovered host device. As part of this step, the PHY manager will ensure TCP/IP connectivity to each such host device.

Now, the method may proceed with injection of the application or driver into the host device(s). At step 404, the method may examine the registry for determining each host device that is connected, as this will determine what specific task(s) must be undertaken for performing injection (i.e., to inject an appropriate application or driver into each such host device). At step 405, a TCP/IP session is established with the host device, for the specific purpose of injecting the file or object of interest (e.g., application or driver). At step 406, the file is opened on the client device; as part of this process, a client-side file handle is obtained. From the perspective of the client device, the file is simply a binary object to be injected. The specific relevance of the file will be uncovered at the host device, when the file is ultimately executed at the host device. Having obtained a valid file handle for the file to be injected at step 406, the method may now proceed to package the file contents for transmission to host device, as indicated at step 407. In the currently-preferred embodiment, the XML protocol is employed for this packaging. Now, using TCP/IP, the packaged file may be transmitted (streamed) from the client device to the host device, as indicated by step 408. In conjunction with this step, a host-side file handle is returned to the client device.

At this point, the method is now ready to trigger execution of the just-injected application or driver at the host device. Using the host-side file handle, the method instructs the host to now execute the just-injected application or driver, as indicated by step 409. As previously described, host-side execution may require host-specific operations. In the straightforward case, the host is simply instructed to begin execution of the application or driver. If the host device does not support that functionality, however, execution of the application or driver may be accomplished through indirect means, such as instructing the host to “restart” itself and thereupon execute the application or driver (e.g., by placing the application or driver in a location where the host will automatically load it for execution upon startup). Thereafter, as indicated by step 410, operation between the client and host devices continues as specified in the now-executing application or driver, which itself in turn may unpackage other drivers for execution. In typical operation, the application or driver would issue particular commands to the client device, for instance, requesting that the client device transmit particular information that is to be processed by the host device (e.g., uploading digital photographs from the client device to the host device, for wireless transmission by the host device).

Camera to phone communications interface

A. Introduction

In accordance with the present invention, a communications interface embodiment is provided between a cellular (GSM) phone, Java bytecode application, and a wireless digital camera (e.g., system 100). This interface describes all the capabilities that are required to implement a UI application.

B. Description of Channels

1. Multi-Channel Communication

(a) General

The digital camera communicates with the GSM phone over a multi-channel I/O bus. This bus uses a TCP/IP-based packet protocol to simulate multiple simultaneous communication channels over multiple sockets. Using this system, the camera software can have several simultaneous conversations with the phone.

The camera makes use of four supplied channels: the Management/Monitor channel, the Event channel, the UI/Command channel, and the Server channel. A common protocol is implemented on the first three channels. This protocol transmits commands and replies as ASCII XML coded data.

(b) Management/Monitor channel

The camera uses the Management channel to upload the Java bytecode application to the phone and to manipulate the application. The application commands include application execution, application termination, and application activation. The phone “listens” on this port and will wait for the camera to connect to this port.

(c) Event channel

The Event channel is used to send event messages between the camera and the phone app. One event is a “heartbeat monitor” for the phone. The phone periodically expects a heartbeat packet in response to a heartbeat request in order for it to consider the camera app still connected. Once a heartbeat is missed, the phone will assume that the camera has been disengaged from the phone (or powered off) and will execute appropriate termination sequences. This is implemented by a Status command that returns the present camera status.

The camera “listens” on this port and accepts a connection on this port. The camera can also query the phone to determine the present status of the phone. This may help the camera determine when to enter aggressive power saving modes of operation. In addition, the camera can send the phone a “photo done” event to indicate a new photo is available.

(d) UI/Command channel

The camera uses the UI channel to establish a direct line of communication between the camera software resident on the camera itself and the Java bytecode application uploaded to the phone. The camera “listens” on this port, and the Java application will connect to the camera on this port. The command structure and state diagrams of this communication are entirely determined by the camera and Java software packages.

(e) Server channel

The camera uses the Server channel to establish a direct communication with a target IP address on the cellular network (or the Internet).

C. XML Protocol

The protocols used for the Management/Monitor channel, Event channel, and UI/Command channels consist of XML data commands and replies. XML is used to support parsing of the command type and the command parameters. Because standard format tags are used, standard XML parsers can be used to extract the command and parameter information for each transfer.

All XML PDUs will start with a tag to indicate the version. This tag is a 2-character value, with the first character indicating the major revision of the PDU and the second character indicating the minor revision of the code. The following is an example: <Ver>“01”</Ver>. This indicates that this is version 0.1 of the protocol.

The protocol insures that the beginning and end of the PDU can be determined. All XML transfers have beginning and end tags to indicate the extent of the packet. These tags are all followed by a carriage return value or newline character value to indicate the end of the present line and the beginning of a new line. This document tag determines what type of command is to be performed.

In addition, commands and replies may include additional parameters used to completely specify the command or reply. The data types supported by the tags are as follows:

-   -   1. ASCII String—a group of ASCII characters. This is not NULL         terminated, and does not contain a length value.     -   2. UI4—a 4 byte unsigned integer as defined in XML.     -   3. UI1—a 1 byte unsigned integer as defined in XML.     -   4. Binary Data—a generic byte buffer. This must be preceded by a         size tag to prevent false end tag values within binary data.     -   5. Enum—this is a 1 byte value that is used to represent an enum         equivalent value. The exact numeric value of all enum types are         documented elsewhere. The byte is interpreted as an unsigned 8         bit value.     -   6. Parent—a tag to indicate the start of a new hierarchy.

The default data value is a string, if not listed otherwise. Presently, all data values are either ASCII string values or Binary Data.

The parser is strict—tags must appear in the order given. All numbers strings must be either in decimal or C style hex format with a prepended 0x.

The following table lists the parameter tag, the tag's type, and a short description of the use of the tag:

Parameter Tag Type Description <name></name> ASCII String Indicates the name of a file, application or photo object. <size></size> ASCII String Size in bytes of a data object. Only associated with binary objects. <fsize></fsize> ASCII String Size in bytes of a file. <status></status> ASCII String This values represents the error state resulting from the execution of a command. All states will return 0(OK), 1(ERR_BAD_CMD), 2(ERR_BAD_TAG), (3)ERR_BAD_PARAM, 4(ERR_FAILED), 5(ERR_NOT_IMPL) or a command specific error value. <handle></handle> ASCII String A 32 bit value to be used to reference a particular application object. <dir></dir> ASCII String A string describing the name of a directory. <priority> ASCII String An enum to indicate the priority of the </priority> execution of the command: HI, NORM or LO. <date></date> ASCII String A date type that is in the following format: (Wed, 17 May 2000) <time></time> ASCII String A character type that is accurate to the second. (11:02:32) <zone></zone> ASCII String A string that describes the offset from GMT time. (−0700) <utc></utc> ASCII String A string that represents the Posix UTC time value. This is defined as the number of seconds since 1 January, 1970. <cameraState> ASCII String An enum representing the state of the camera: </cameraState> ERROR, SLEEP, BUSY, READY. <phoneState> ASCII String An enum representing the state of the phone: </phoneState> ERROR, SLEEP, BUSY, READY. <photoState> ASCII String An enum representing the state of a photo: </photoState> LOCAL, TAG, SENT. <text></text> ASCII String Represents a text string. <width></width> ASCII String A 32 bit value representing the width of a picture object. <height></height> ASCII String A 32 bit value representing the height of a picture object. <aspectwidth> ASCII String A float value representing the aspect width of </aspectwidth> a picture object. This is used in conjunction with the aspectheight value. <aspectheight> ASCII String A float value representing the height of a </aspectheight> picture object. This is used in conjunction with the aspectwidth value. <depth></depth> ASCII String An 8 bit value representing the bits per pixel of a picture object. The tested values are 1 and 2. <color></color> ASCII String An enum representing the type of color mechanism used to implement the depth. Presently the only value supported is BW. <type></type> ASCII String A string to indicate the type of picture object. The valid values are alien_preview, generic, low, med, high, full, anc and tagged. NOTE: tagged is not supported by the CamGetPicture command. Anc, low, med, high are not supported by the CamGetPhotoDir command. <num></num> ASCII String A 32 bit quantity to indicate the number of (32 bit number) elements to be returned. <bin></bin> Parent Tag This tag is used to indicate the presence of binary data. <file></file> Parent Tag This tag is used to indicate the following information is associated with a particular file. <datetime> Parent Tag This tag indicates that the following tags </datetime> describe the date, time and zone information. <email_list> Parent Tag This tag indicates the following tags describe </email_list> email addresses. <email></email> Parent Tag This tag encloses subtags to represent data for email transmission. <alias></alias> ASCII String This string is used to represent the full name or other alias given to a particular email address. <emailadd> ASCII String A string to represent an email address. </emailadd> <album_list> Parent Tag This tag indicates the following tags describe </album_list> Photo Album names. <album></album> ASCII String A string to represent an album name.

All XML examples are presented in a consistent manner. This presentation will differ in one aspect from the above specification. The sub tags of the overall command tags are indented four spaces for readability. The following is an example of a command message PDU:

<Ver>13</Ver> <LoadApp> <name>Vcam</name> <bin> <size> (value) </size> Replace (value) with actual value (data) Replace (data) with actual data </bin> </LoadApp>

D. Management/Monitor Channel

The Management channel is used to discover what device is connected to the camera, as well as perform any device-specific initialization actions on the attached device.

The following section describes the functions available after communications have been established with the phone. This communication will occur on Port 13000. The phone is the master of this channel and will be accepting connections to this port.

1. Load Application

The following is the process to load the Java bytecode application from the camera to the phone:

EXAMPLE #1 Camera ->Phone

<LoadApp> <name> (app) </name> <bin> <size> (value) </size> The size of the data in bytes (data) The Java bytecode binary data </bin> </LoadApp>

EXAMPLE #2 Camera<- Phone

<LoadAppR> <status> (value) </status> Standard error replies or ERR_TOO_BIG <handle> (value) </handle> A handle to represent the app </LoadAppR>

2. Release Application

The Release Application command is sent to indicate that the application can be deleted from the phone. The following is the process to release control of the application loaded into the phone:

EXAMPLE #1 Camera ->Phone

<ReleaseApp> <handle> (value) </handle> A handle to represent the app </ReleaseApp>

EXAMPLE #2 Camera<- Phone

<ReleaseAppR> <status> (value) </status> Standard error replies or ERR_BAD_HAND </ReleaseAppR>

3. Start Application

To start the application, the following process should be used:

EXAMPLE #1 Camera ->Phone

<StartApp> <handle> (value) </handle> A handle to represent the app </StartApp>

EXAMPLE #2 Camera<- Phone

<StartAppR> <status> (value) </status> Standard errors or ERR_BAD_HAND, ERR_RESOURCE </StartAppR>

4. Activate Application

The following process will allow the camera to activate an already-running application and bring the main application window to the foreground:

EXAMPLE #1 Camera ->Phone

<ActivateApp> <handle> (value) </handle> A handle to represent the app <priority> (value) </priority> Priority = HI, NORM, LO </ActivateApp>

EXAMPLE #2 Camera<- Phone

<ActivateAppR> <status> (value) </status> Standard error replies or ERR_BAD_HAND </ActivateAppR>

5. Stop Application

A Stop Application command will terminate an application if it is running. A priority value will indicate the urgency to use when stopping the application. To stop an executing application, the following process should be used:

EXAMPLE #1 Camera ->Phone

<StopApp> <handle> (value) </handle> A handle to represent the app <priority> (value) </priority> Priority = HI, NORM, LO </StopApp>

EXAMPLE #2 Camera<- Phone

<StopAppR> <status> (value) </status> Standard error replies or ERR_BAD_HAND </StopAppR>

6. Get Capabilities

The following process will allow the camera to login to a device listening on the Management channel:

EXAMPLE #1 Camera ->Phone

<GetCap> </GetCap>

EXAMPLE #2 Camera<- Phone

<GetCapR> <status> (value) </status> Standard error replies <lang> (value) </lang> Present language (English, etc.) <id> (value) </id> id of device <imei> (value) </imei> imei of device <imsi> (value) </imsi> imsi of device <screen> (value) </screen> Display capabilities <version> (value) </version> Version of code <dataLink> (value) </dataLink> Quality of data link <flash> (value) </flash> Flash capability <cpu> (value) </cpu> Standard error replies </GetCapR>

7. Get Active Application Handle

The Get Active Application Handle command is documented for completeness. There are no current plans to use this command. The following process will retrieve the handle of the currently-active application running on the phone:

EXAMPLE #1 Camera ->Phone

<GetActAppHandle> </GetActAppHandle>

EXAMPLE #2 Camera<- Phone

<GetActAppHandleR> <status> (value) </status> Standard error replies <handle> (value) </handle> Handle to the application </GetActAppHandleR>

8. Start Camera Application

To start the application, the following process should be used:

EXAMPLE #1 Camera ->Phone

<StartCameraApp> </StartCameraApp>

EXAMPLE #2 Camera<- Phone

<StartCameraAppR> <status> (value) </status> Standard errors or ERR_BAD_HAND, ERR_RESOURCE </StartCameraAppR>

E. Event Channel

The Event channel is a bi-directional channel to be used to share events with an attached device. Both the camera and the phone will query each other to determine if there are any changes in status that will affect operation. This communication will occur on Port 13001. The camera listens on this port and will accept connections to this port.

1. Status (Phone)

The camera will also be capable of periodically querying the phone using a Status packet to test the phone's status. The following process is used to get status on the phone:

EXAMPLE #1 Camera ->App

<PhoneStatusEvent> </PhoneStatusEvent>

EXAMPLE #2 Camera<- App

<PhoneStatusEventR> <status> (value) </status> Standard error replies <phoneState> (state) </phoneState> state = ERROR, SLEEP, BUSY or READY </PhoneStatusEventR>

2. Photo Done

To notify the application that a new picture has been taken during this session, the camera will send this message to the phone:

EXAMPLE #1 Camera ->App

<PhonePhotoDoneEvent> <name> (file name) </name> </PhonePhotoDoneEvent>

EXAMPLE #2 Camera<- App

<PhonePhotoDoneEventR> <status> (value) </status> Standard error replies </PhonePhotaDoneEventR>

3. Photo State Change

To notify the application that a photo has changed state (sent to server) during this session, the camera will send this message to the phone:

EXAMPLE #1 Camera ->App

<PhonePhotoStateEvent> <name> (file name) </name> <photoState> (state) </photoState> Where state is LOCAL, TAG or SENT </PhonePhotoStateEvent>

EXAMPLE #2 Camera<- App

<PhonePhotoStateEventR> <status> (value) </status> Standard error replies </PhonePhotoStateEventR>

4. Phone Message Box

The following command allows the camera to send a string to the phone application. This string is then displayed in a message box to the user. Optionally, a data entry field can be specified. To send the text, send the following:

EXAMPLE #1 Camera ->App

<PhoneMessageBox> <text> (message) </text> <mboxType> (data) </mboxType> Type of Message Box to display </PhoneMessageBox>

EXAMPLE #2 Camera<- App

<PhoneMessageBoxR> <status> (value) </status> Standard error replies <text> (data)</text> Optional data entered by user </PhoneMessageBoxR>

The mboxType is a numeric ASCII value specifying the type of message box to display. The only two values are 0 and 1. A static text only message box is indicated by the value 0. A message box with a single text entry item has a value of 1. No other values are supported in this revision.

A user may cancel a text entry message box. The status value returned in the reply will indicate if the user has canceled the operation. If the user has entered a value and has continued, the status will indicate OK and a text value will be returned in the reply which is the value entered by the user. The status returns would be represented by numeric ASCII values as defined by the following C/C++ statement:

typedef enum { UICHAN_OK, UICHAN_BAD_CMD, UICHAN_BAD_TAG, UICHAN_BAD_PARAM, UICHAN_FAILED, UICHAN_NOT_IMPL, UICHAN_CANCELED } UICHAN_STATUS_E;

5. Phone Server Connected Event

The following command tells the phone that the camera has successfully connected to a photo server. This is in response to a UI/Command Channel Contact Server command. The syntax is as follows:

EXAMPLE #1 Camera ->App

<PhoneServerConnectedEvent> </PhoneServerConnectedEvent>

EXAMPLE #2 Camera<- App

<PhoneServerConnectedEventR> <status> (value) </status> Standard error replies </PhoneServerConnectedEventR>

6. Phone Server Done Event

The following event tells the phone that the server has finished its connection with the camera, and the data call can be safely terminated. This is in response to a UI/Command Channel Contact Server command. The syntax is as follows:

EXAMPLE #1 Camera ->App

<PhoneServerDoneEvent> </PhoneServerDoneEvent>

EXAMPLE #2 Camera<- App

<PhoneServerDoneEventR> <status>(value)</status> Standard error replies </PhoneServerDoneEventR>

7. Photo Transfer Event

This event tells the camera application how much of the photo has been transferred. These events are sent only when a significant amount of data has been transferred from the camera. The 100% event may not be sent, as there is a separate Photo State event to indicate when the photo has been successfully transferred. The following is the syntax to send the Photo Transfer Event:

EXAMPLE #1 Camera ->App

<PhonePhotoTransferEvent> <name>(file name)<name> <percent>(data)</percent> </PhonePhotoTransferEvent>

EXAMPLE #2 Camera<- App

<PhonephotoTransferEventR> <status>(value)</status> Standard error replies <PhonePhotoTransferEventR>

The percent is an integer ASCII value specifying the percent of the photo that has been transferred.

F. UI/Command Channel

This communication protocol is completely under the control of the camera since the camera uploads the application that will communicate over this channel. The following is the communications that will be supported between the camera and the Java bytecode application. This communication will be conducted over Port 13002. The camera is the master of this port and will accept connections on this port.

1. Set Time

To allow the camera to synchronize time with the application, the application will send the camera a message to set the current time. The message is as follows:

EXAMPLE #1 Camera<- App

<CamSetTime> <datetime> <date>Mon, 12 June, 2000</date> <time>11:32:06</time> <zone>-0800</zone> <utc>16083360</utc> </datetime> </CamSetTime>

EXAMPLE #2 Camera ->App

<CamSetTimeR> <status>(value)</status> Standard error replies </CamSetTimeR>

2. Get Time

This message will allow the application to query the camera to support time synchronization. The process is as follows:

EXAMPLE #1 Camera<- App

<CamGetTime> </CamGetTime>

EXAMPLE #2 Camera ->App

<CamGetTimeR> <status>(value)</status> Standard error replies <datetime> <date>Mon, 12 June, 2000</date> <time>11:32:06</time> <zone>-0800</zone> <utc>16083360</utc> </datetime>\n </CamGetTime

3. Set Photo State

The following process will embed the Photo State within a specific file:

EXAMPLE #1 Camera<- App

<CamSetPhotoState> <name>(photo)</name> <stateType>(value)</stateType> 0 for simple, 1 for detailed <photoState>(state)</photoState> (LOCAL, TAG or SENT for simple) <photoStateDetail>(state)</photoStateDetail> (see below. Detail only) </CamSetPhotoState>

EXAMPLE #2 Camera ->App

<CamSetPhotoStateR> <status>(value)</status> Standard error replies or ERR_BAD_NAME </CamSetPhotoStateR>

The stateType value is optional. If not present, the simple state will be returned. The simple state has three states: LOCAL, TAG or SENT. The detailed state adds one photoState to the simple photo state: DONE. The detailed photo state, photoStateDetail, returns the number of photo compartments that have been sent. This is interpreted as an ASCII integer value. The current design specification is for a maximum of 64 compartments.

4. Get Photo State

The following process will retrieve the Photo State within a specific file:

EXAMPLE #1 Camera<- App

<CamGetPhotoState> <name>(photo)</name> <stateType>(value)</stateType> 0 for simple, 1 for detailed </CamGetPhotoState>

EXAMPLE #2 Camera ->App

<CamGetPhotoStateR> <status>(value)</status> Standard error replies or ERR_BAD_NAME <photoState>(state)</PhotoState> Where state is LOCAL, TAG or SENT <photoStateDetail>(state)</photoStateDetail> (see below. Detail only) </CamGetPhotoStateR>

The stateType value is optional. If not present, the simple state will be returned. The simple state has three states: LOCAL, TAG or SENT. The detailed state adds one photoState to the simple photo state: DONE. The detailed photo state, photoStateDetail, returns the number of photo compartments that have been sent. This is interpreted as an ASCII integer value. The current design specification is for a maximum of 64 compartments.

5. Set Photo Data

The following process will send ancillary photo data to the camera for future use by the Server or the phone:

EXAMPLE #1 Camera<- App

<CamSetPhotoData> <name>(photo)</name> <title>My Picture</title> <location>Sydney Australia</location> <comments>My father age 64, my mother age 62</comments> <email_list>\n <email> <alias>User Name</alias>\n <emailadd>user@isp.com</emailadd>\n </email> <email> <alias>Mini Me</alias>\n <emailadd>me@isp.com</emailadd>\n </email> </email_list>\n <album_list> <album>Travel</album> <album>Holiday</album> </album_list> </CamSetPhotoData>

EXAMPLE #2 Camera ->App

<CamSetPhotoDataR> <status>(value)</Status> Standard error replies or ERR_BAD_NAME </CamSetPhotoDataR>

6. Get Photo Data

The following process will retrieve the ancillary photo data for a particular photo:

EXAMPLE #1 Camera<- App

<CamGetPhotoData> <name>(photo)</name> </CamGetPhotoData> <CamGetPhotoDataR> <status>(value)</status> Standard error replies or ERR_BAD_NAME <title>My Picture</title> <location>Sydney Australia</location> <comments>My father age 64, my mother age 62</comments> <email_list> <emailadd>user@isp.com</emailadd> <emailadd>me@isp.com</emailadd> </email_list> <album_list> <album>Travel</album> <album>Holiday</album> </album_list> </CamGetPhotoDataR>

EXAMPLE #2 Camera ->App

<CamGetPhotoDataR>   <status>(value)</status>  Standard error replies or   ERR_BAD_NAME   <title>My Picture</title>   <location>Sydney Australia</location>   <comments>My father age 64, my mother age 62</comments>   <email_list>     <emailadd>user@isp.com</emailadd>     <emailadd>me@isp.com</emailadd>   </email_list>   <album_list>     <album>Travel</album>     <album>Holiday</album>   </album_list> </CamGetphotoDataR>

7. Set Album

The following process will send album data to the camera for future use by the Server or the phone:

EXAMPLE #1 Camera<- App

<CamSetAlbum> <album_list> <album>Travel</album> <album>Holiday</album> </album_list> </CamSetAlbum>

EXAMPLE #2 Camera ->App

<CamSetAlbumR> <status>(value)</status> Standard error replies or ERR_BAD_NAME </CamSetAlbumR>

8. Get Album

The following process will retrieve the album data from the phone:

EXAMPLE #1 Camera<- App

<CamGetAlbum> </CamGetAlbum>

EXAMPLE #2 Camera ->App

<CamGetAlbumR> <status>(value)</status> Standard error replies or ERR_BAD_NAME <album_list> <album>Travel</album> <album>Holiday</album> </album_list> </CamGetAlbumR>

9. Get Picture

The following process will send a picture file from the camera to the application. Not all parameters are required for all picture types.

EXAMPLE #1 Camera<- App

<CamGetPicture> <name>(photo)</name> <width>(value)</width> <height>(value)</height> <aspectwidth>(value)</aspectwidth> A text representation of a float <aspectheight>(value)</aspectheight> A text representation of a float <depth>(value)</depth> The number of bits per pixel(1) <color>(value)</color The type of display (BW) <type>(value)</type> The type of image to retrieve (BITMAP) <startByte>(data)</startByte> Start byte of data <fsize>(data)</fsize> Number of bytes <startPercent>(data)</startPercent> Start percent for UI events <endPercent>(data)</endPercent> End percent for UI events </CamGetPicture>

EXAMPLE #2 Camera ->App

<CamGetPictureR> <status>(value)</status> Standard error replies or ERR_BAD_NAME <bin> <size>(value)</size> Value is number of bytes of Data (data) Data is the requested image </bin> </CamGetPictureR>

The <startByte> and <fsize> values are optional. These values allow retrieval of partial images. If these tags are not present, the whole file will be returned. This value only applies to native progressive picture formats.

The <startPercent> and <endpercent> values are also optional. These values can be used to indicate to the camera the UV update range for a particular picture transfer. This allows Host to dictate to the camera how the UI photo events will be handled.

10. Contact Server

The following process will cause the camera to initiate a connection to a Server through the Server channel:

EXAMPLE #1 Camera<- App

<CamCallServer> </CamCallServer>

EXAMPLE #2 Camera ->App

<CamCallServerR> <status>(value)</status> Standard error replies </CamCallServerR>

The reply from the camera does not indicate that the Server connection has been made. A separate asynchronous Server Connected event on the Event Channel indicates when the connection has been made. A Server Done event on the Event Channel indicates when the call is complete. If an error occurs in connection and a connection was never made, a Server Done event with an error code will be sent without a Server Connected event.

A subsequent Contact Server command should not be sent before a Server Done event on the Event channel has been received from the last Contact Server command.

11. Hangup Server

The following process will cause the camera to terminate the current Server connection:

EXAMPLE #1 Camera<- App

<CamHangupServer> </CamHangupServer>

EXAMPLE #2 Camera ->App

<CamHangupserverR> <status>(value)</status> Standard error replies </CamHangupServerR>

The reply from the camera does not indicate that the Server connection has been disconnected. A separate asynchronous Server Done event on the Event Channel indicates when the Server connection has been terminated.

12. Delete Rile

The following process will delete a file from the camera:

EXAMPLE #1 Camera<- App

<CamFDel> <name>(value)</name> </CamFDel>

EXAMPLE #2 Camera ->App

<CamFDelR> <status>(value)</status> Standard error replies or ERR_BAD_NAME </CamFDelR>

13. Delete Photo

The following process will delete a file from the camera:

EXAMPLE #1 Camera<- App

<CamPDel> <name>(value)</name> </CamPDel>

EXAMPLE #2 Camera ->App

<CamPDelR> <status>(value)</status> Standard error replies or ERR_BAD_NAME </CamPDelR>

14. Photo Directory

To get a listing of photos on the camera, the application will use this process:

EXAMPLE #1 Camera<- App

<CamPDir> <type>(value)</type> alien_review, full, tagged </CamPDir>

EXAMPLE #2 Camera ->App

<CamPDirR> <status> (value) </status> Standard error replies <num> (value) </num> Number of file names <name> (file1) </name> <name> (file2) </name> . . . </CamPDirR>

15. File Directory

To get a listing of files on the camera, the application will use this process:

EXAMPLE #1 Camera<- App

<CamFDir> <dir> (directory) </dir> </CamFDir>

EXAMPLE #2 Camera ->App

<CamFDirR> <status> (value) </status> Standard error replies <num> (value) </num> Number of file names <file> <name> (file1) </name> <fsize> (size) </fsize> <date> (date) </date> </file> <file> <name> (file2) </name> <fsize> (size) </fsize> <date> (date) </date> </file> . . . </CamFDirR>

16. Send File

The application can send a file (either a photo or application file) to the camera. This can be used for upgrading code as well as photo sharing. Use this process to send a file to the camera:

EXAMPLE #1 Camera<- App

<CamSendFile> <name> (value) </name> Name of the file <bin> <size> (value) </sixe> Value is number of bytes of Data (data) Data is the requested image </bin> </CamSendFile

EXAMPLE #2 Camera ->App

<CamSendFileR> <status> (value) </status> Standard error replies or ERR_BAD_NAME /CamSendFileR>

17. Get File

The following process will send a file from the camera to the application:

EXAMPLE #1 Camera<- App

<CamGetFile> <name> (file) </name> Name of the file <startByte> (data) </startByte> Start byte of data <fsize> (data) </fsize> Number of bytes </CamGetFile>

EXAMPLE #2 Camera ->App

<CamGetFileR> <status> (value) </status> Standard error replies or ERR_BAD_NAME <bin> <size> (value) </sixe> Value is number of bytes of Data (data) Data is the requested image <bin> </CamGetFileR>

The <startByte> and <fsize> values are optional. These values allow retrieval of partial files. If these tags are not present, the whole file will be returned.

18. Camera Info

This command indicates that the user has selected a menu item indicating they wish to view the camera information. The following command and reply set specify a mechanism to indicate to the camera that this information has been requested. A separate Event Channel message, Phone Message Box, as described above, will be used to display the information for the user.

The following command indicates that the Camera Info menu item has been selected:

EXAMPLE #1 Camera<- App

<CamInfoMenu> </CamInfoMenu>

EXAMPLE #2 Camera ->App

<CamInfoMenuR> <status> (value) </status> Standard error replies </CamInfoMenuR>

19. Camera Set Sound State

This command will turn the camera sounds on or off. A parameter in the command packet will indicate if the sound will be turned on or off. The sound state will be preserved across power cycles.

EXAMPLE #1 Camera<- App

<CamSetSoundState> <soundState> (value) </soundState> </CamSetSoundState>

EXAMPLE #2 Camera ->App

<CamSetSoundStateR> <status> (value) </status> Standard error replies </CamSetSoundStateR>

The soundState value is an integer ASCII value specifying whether the sound is enabled (1) or disabled (0).

20. Camera Get Sound State

This command will query the camera to determine whether the camera sounds are on or off.

EXAMPLE #1 Camera<- App

<CamGetSoundState> </CamGetSoundState>

EXAMPLE #2 Camera ->App

<CamGetSoundStateR> <status> (value) </status> Standard error replies <soundState> (value) </soundState> </CamGetSoundStateR>

The soundState value is an integer ASCII value specifying whether the sound is enabled (1) or disabled (0).

21. File Formats

The following table describes the file extensions and formats that are available on the camera.

File Type File Extension Description Photo none The photo file is the base name for all of the files associated with a photo. Preview 1 none A preview image is created dynamically. Progressive Photo .ppf LightSurf proprietary photo format (described, e.g., in Format the above-mentioned 09/537,001 application). Tag File .tag This zero length file indicates that a photo is ready to be sent to the Photo Server. Sent File .snt This zero length file indicates that a photo has been successfully sent to the Photo Server. Ancillary Data .anc This file contains the Title, Location, Comments, E- mail address list, album, timestamp, and other items used to describe the photo image.

G. Server Channel

This channel will be used to open a connection between the Photo Server and the camera. This allows photo and file transfer between a LightSurf Server and the camera. The data sent between the camera and the Server is completely independent of the phone. The phone will only forward the packets sent on this channel. The Server communications will be based on the UI channel communications.

While the invention is described in some detail with specific reference to a single-preferred embodiment and certain alternatives, there is no intent to limit the invention to that particular embodiment or those specific alternatives. For instance, those skilled in the art will appreciate that modifications may be made to the preferred embodiment without departing from the teachings of the present invention. 

1. In a computer environment where devices are occasionally connected together, a method for automated transmission and execution of an executable file of interest originating from a digital camera, upon the digital camera's connection to a cellular phone, the method comprising: connecting the digital camera to a cellular phone capable of hosting the camera; identifying at least one particular cellular phone that is connected to the camera, including determining communication information allowing communication between the camera and the particular cellular phone, and determining command information allowing the camera to invoke execution of a file of interest at the particular cellular phone; based on said determined communication information, transmitting the executable file of interest from said camera to the particular cellular phone; and based on said determined command information, invoking execution of the executable file of interest after it has been transmitted to the particular cellular phone.
 2. The method of claim 1, wherein said executable file of interest comprises a driver file.
 3. The method of claim 2, wherein said driver file, upon execution, controls operation of said camera.
 4. The method of claim 1, wherein said executable file comprises one of a machine instruction for a target processor and a Java bytecode instruction for a Java virtual machine.
 5. The method of claim 1, wherein said executable file comprises an application program capable of executing at said cellular phone.
 6. The method of claim 1, wherein said camera includes an add-in device capable of being hosted by said cellular phone.
 7. The method of claim 6, wherein said camera comprises a digital camera and wherein said method further comprises: upon execution of said executable file at said cellular phone, transferring image information from said digital camera to said cellular phone.
 8. At the method of claim 7, further comprising: after transferring said image information from said digital camera to said cellular phone, wirelessly transmitting said image information to a third device.
 9. The method of claim 1, wherein said cellular phone includes a computing device capable of hosting other devices.
 10. The method of claim 1, wherein said cellular phone includes wireless transmission capability for transferring information received from said camera to other devices.
 11. The method of claim 1, wherein said camera and cellular phones are occasionally connected together.
 12. The method of claim 1, wherein said camera and cellular phones are permanently connected together.
 13. The method of claim 1, wherein said camera and cellular phones are connected together via a serial communication link.
 14. The method of claim 13, wherein said serial communication link comprises an RS-232 serial communication link.
 15. The method of claim 1, wherein said camera and cellular phones are connected together via a USB (Universal Serial Bus) link.
 16. The method of claim 1, wherein invocation of said identifying step occurs upon connecting said camera and cellular phones together.
 17. The method of claim 1, wherein said identifying step includes: probing the camera's environment for determining which devices, if any, the camera is attached to.
 18. The method of claim 17, wherein said probing step includes: determining a default communication medium for probing for new devices.
 19. The method of claim 18, wherein said default communication medium is specified initially by factory-preset information.
 20. The method of claim 18, wherein said default communication medium is a selected one of a wireless and a wired communication medium.
 21. The method of claim 20, wherein said default communication medium includes a serial (RS-232) and a USB (Universal Serial Bus) wired communication medium.
 22. The method of claim 19, wherein said factory-preset information is stored in a registry of the camera.
 23. The method of claim 19, wherein said factory-preset information includes a default communication rate and default handshake protocol for at least one potential cellular phone.
 24. The method of claim 17, wherein said probing step includes: executing an initial sequence of handshake commands and comparing any response received to a list of known responses for identifying a particular cellular phone.
 25. The method of claim 17, wherein said probing step continues until all known potential cellular phones have been enumerated.
 26. The method of claim 1, wherein said identifying step includes: updating a registry at said camera for indicating any connected cellular phone that has been identified.
 27. The method of claim 1, further comprising: upon identifying at least one particular cellular phone, ensuring that a state of TCP/IP communication is reached between said camera and the particular identified cellular phone.
 28. The method of claim 27, wherein said step of ensuring that a state of TCP/IP communication is reached includes: initiating a PPP (Point-to-Point Protocol) communication session between said camera and cellular phones; and, thereafter initiating a TCP/IP communication session between said camera and cellular phones.
 29. The method of claim 27, wherein said step of ensuring that a state of TCP/IP communication is reached includes: determining an IP (Internet Protocol) address for said cellular phone.
 30. The method of claim 1, wherein said step of transmitting the executable file of interest includes: opening the executable file of interest at the camera; and streaming the opened executable file of interest from the camera to the cellular phone.
 31. The method of claim 30, wherein said streaming step includes: employing XML protocol for packaging said executable file of interest for delivery to the cellular phone.
 32. The method of claim 30, wherein said step of transmitting further comprises: returning to said camera a file handle permitting said camera to access said executable file of interest transmitted to said cellular phone.
 33. The method of claim 31, wherein said file handle comprises a file handle that may be understood by said cellular phone for accessing a particular file of interest at said cellular phone.
 34. The method of claim 1, wherein said executable file of interest comprises a byte-code program, and wherein said cellular phone includes capability for executing byte-code programs.
 35. The method of claim 1, wherein said executable file of interest comprises a Java program, and wherein said cellular phone includes a Java Virtual Machine for executing Java programs.
 36. The method of claim 1, wherein said step of invoking execution of the executable file of interest includes: issuing a command from said camera to said cellular phone to begin execution at said cellular phone of said executable file of interest.
 37. The method of claim 1, wherein said step of invoking execution of the executable file of interest includes: triggering execution of said executable file indirectly at said cellular phone by instructing said cellular phone to restart itself.
 38. The method of claim 1, further comprising: placing said camera in a listening mode, after said camera has invoked execution of said executable file at said cellular phone.
 39. The method of claim 38, wherein said camera awaits commands from said cellular phone, while said camera is in a listening mode.
 40. The method of claim 39, wherein commands received at said camera from said cellular phone control operation of said camera.
 41. A mufti-device system providing automated loading and execution of a driver required for connected devices, the system comprising: a camera that may be connected to a cellular phone that is capable of hosting the camera; and a subsystem, incorporated in the camera, for automatically: (i) identifying the cellular phone upon connection to the camera, said subsystem initiating communication between the two devices; (ii) uploading the driver of interest from the camera to the cellular phone; and (iii) transmitting at least one command from the camera that invokes execution of the driver of interest at the cellular phone, whereupon the driver executes at the cellular phone for controlling operation of the camera.
 42. The system of claim 41, wherein said driver comprises a binary file having instructions capable of executing at said cellular phone.
 43. The system of claim 42, wherein said binary file comprises native machine instructions for execution by a processor at said cellular phone.
 44. The system of claim 42, wherein said binary file comprises byte-code instructions for execution by an interpreter at said cellular phone.
 45. The system of claim 44, wherein said binary file comprises a Java program, and wherein said cellular phone includes a Java Virtual Machine for executing Java programs.
 46. The system of claim 44, wherein said driver includes: instructions for unpacking other executable files for execution at said cellular phone.
 47. The system of claim 41, wherein said camera comprises an add-in device capable of being hosted by said cellular phone.
 48. The system of claim 47, wherein said camera comprises a digital camera device, and wherein said cellular phone comprises a handheld device capable of hosting said digital camera device.
 49. The system of claim 48, wherein said handheld computing device functions to retrieve digital image information from said digital camera device and wirelessly transmit that information to another system.
 50. The system of claim 48, wherein said handheld device is a selected one of a cellular phone device and a handheld computing device.
 51. In a computer environment where devices are occasionally connected together, a method for automated transmission, execution, and manipulation of an executable file of interest originating from a first device, upon the first device's connection to a host device, the method comprising: connecting the first device to at least one other device capable of hosting the first device; identifying at least one particular host device that is connected to the first device, including determining communication information allowing communication between the first device and the particular host device, and determining command information allowing the first device to manipulate and invoke execution of an executable file of interest at the particular host device; based on said determined communication information, transmitting the executable file of interest from said first device to the particular host device; based on said determined command information, transmitting from said first device to the particular host device commands that manipulate the executable file of interest at the particular host device; and initiating a dialog between the two devices, including: (i) executing said commands transmitted to the host device on the host device, and (ii) in response to said commands transmitted to the host device, returning a reply from the host device to the first device.
 52. The method of claim 51, wherein said commands include a command to load the executable file of interest.
 53. The method of claim 51, wherein said commands include a command to start the executable file of interest.
 54. The method of claim 51, wherein said commands include a command to end the executable file of interest.
 55. The method of claim 51, wherein said commands include a command to activate the executable file of interest.
 56. The method of claim 51, wherein said commands include a command to get the capabilities of the host device.
 57. The method of claim 51, wherein said commands include a command to get a reference to the executable file of interest that is running on the host device.
 58. The method of claim 51, wherein said executable file of interest comprises a Java program, and wherein said host device includes a Java Virtual Machine for executing Java programs.
 59. The method of claim 51, wherein said executable file of interest comprises a byte-code program, and wherein said host device includes capability for executing byte-code programs.
 60. The method of claim 51, further comprising: placing said host device in a listening mode to receive commands from said first device.
 61. The method of claim 51, further comprising: after said first device has transmitted a command to said host device, placing said first device in a listening mode to receive a reply transmitted from said host device.
 62. The method of claim 51, wherein said reply transmitted from the host device in response to said command from the first device includes status information.
 63. The method of claim 62, wherein said status information includes error information indicating an execution state of a preceding command executed at the host device.
 64. The method of claim 51, wherein transmission between the devices employs XML protocol.
 65. The method of claim 51, further comprising: returning to said first device a file handle permitting said first device to access said executable file of interest while it resides at said host device.
 66. The method of claim 65, wherein said file handle comprises a file handle that may be understood by said host device for accessing a particular file of interest at said host device.
 67. The method of claim 51, wherein said dialog includes: issuing a load application command from said first device to said host device to receive said executable file of interest transmitted from the first device.
 68. The method of claim 67, wherein the load application command is transmitted from the first device to the host device as an XML stream with a syntax of: <LoadApp> <name> (app) </name> <bin> <size> (value) </size> (data) </bin> </LoadApp>.


69. The method of claim 67, wherein the reply to the load application command is transmitted by the host device to the first device as an XML stream with a syntax of: <LoadAppR> <status> (value) </status> <handle> (value) </handle> </LoadAppR>.


70. The method of claim 51, wherein said dialog includes: issuing a release application command from said first device to said host device to be able to delete said executable file of interest.
 71. The method of claim 70, wherein the release application command is transmitted from the first device to the host device as an XML stream with a syntax of: <ReleaseApp> <handle> (value) </handle> </ReleaseApp>.


72. The method of claim 70, wherein a reply to the release application command is transmitted by the host device to the first device as an XML stream with a syntax of: <ReleaseAppR> <status> (value) </status> </ReleaseAppR>.


73. The method of claim 51, wherein said dialog includes: issuing a start application command from said first device to said host device to begin execution at said host device of said executable file of interest.
 74. The method of claim 73, wherein the start application command is transmitted from the first device to the host device as an XML stream with a syntax of: <StartApp> <handle> (value) </handle> //Handle to application </StartApp>.


75. The method of claim 73,wherein the reply to the start application command is transmitted by the host device to the first device as an XML stream with the following syntax: <StartAppR> <status> (value) </status> //Standard error replies </StartAppR>.


76. The method of claim 51, wherein said dialog includes: issuing a stop application command from said first device to said host device to discontinue execution at said host device of said executable file of interest.
 77. The method of claim 76, wherein the stop application command is transmitted from the first device to the host device as an XML stream with a syntax of: <StopApp> <handle> (value) </handle> <priority> (value) </priority> </StopApp>.


78. The method of claim 76, wherein the reply to the stop application command is transmitted by the host device to the first device as an XML stream with a syntax of: <StopAppR>  <status>(value)</status> </StopAppR>.


79. The method of claim 51, wherein said dialog includes: issuing an activate application command from said first device to said host device to bring current execution of said executable file of interest to the forefront at said host device.
 80. The method of claim 79, wherein the activate application command is transmitted from the first device to the host device as an XML stream with a syntax of: <ActivateApp>  <handle>(value)</handle>  <priority>(value)</priority> </ActivateApp>.


81. The method of claim 79, wherein a reply to the activate application command is transmitted by the host device to the first device as an XML stream with a syntax of: <ActivateAppR>  <status>(value)</status> </ActivateAppR>.


82. The method of claim 51, wherein said dialog includes: issuing a command to get information about device capabilities of said host device.
 83. The method of claim 82, wherein the device capabilities command is transmitted from the first device to the host device as an XML stream with a syntax of: <GetCap> </GetCap>.


84. The method of claim 82, wherein the reply to the get capabilities command is transmitted by the host device to the first device as an XML stream with a syntax of: <GetCapR>  <status>(value)</status>  <lang>(value)<lang>  <id>(value)</id>  <imei>(value)</imei>  <imsi>(value)</imsi>  <screen>(value)</screen>  <version>(value)</version>  <dataLink>(value)</dataLink>  <flash>(value)</flash>  <cpu>(value)</cpu> </GetCapR>.


85. The method of claim 51, wherein said dialog includes: issuing a command to get information about an active application handle for the executable file of interest.
 86. The method of claim 85, wherein the command to get information about an active application handle is transmitted from the first device to the host device as an XML stream with a syntax of: <GetActAppHandle> </GetActAppHandle>.


87. The method of claim 85, wherein a reply to the command to get information about an active application handle is transmitted by the host device to the first device as an XML stream with a syntax of: <GetActAppHandleR>  <status>(value)</status>  <handle>(value)</handle> </GetActAppHandleR>. 